[kwin] [Bug 459468] Certain Xwayland apps do not respect third-party cursor theme on Wayland

[Naxdy]

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

--- Comment #25 from Naxdy  ---
@Andres did you confirm that the flatpak apps in question have read access to
~/.icons and/or /usr/share/icons (or wherever your cursor theme is located),
and that their XCursor search path isn't being overwritten using an environment
variable?

You can use Flatseal to check this, or KDE's built-in permissions system in
System Settings -> Applications -> Flatpak Permission Settings

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

[dolphin] [Bug 472418] New: Dolphin crashes when when screen on after screen saver

[ALeXaNDeR]

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

Bug ID: 472418
   Summary: Dolphin crashes when when screen on after screen saver
Classification: Applications
   Product: dolphin
   Version: 22.12.3
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: alexpr...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-24-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.04
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
After the timeout, the computer screen went blank, but it was not locked.
After the screen woke up, the dolphin crashed.
A second monitor is connected to the laptop via HDMI. This happens periodically
when the screen wakes up after a short sleep.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  __memcpy_evex_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#5  0x7f3bb7ad353a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x7f3bb7ad3b59 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x7f3bb7ad44a9 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x7f3bbdf0a0c2 in QBackingStore::flush(QRegion const&, QWindow*, QPoint
const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x7f3bbe579787 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7f3bbe57b339 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7f3bbe57d4d8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f3bbe5c7a01 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f3bbe5cb7eb in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f3bbe56bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f3bbd8bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f3bbdd3e8f4 in
QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x7f3bbdd164bc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x7f3bb7ade54e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#19 0x7f3bbb71549d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f3bbb770178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f3bbb7141b0 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f3bbd914e7a in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f3bbd8b97cb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f3bbd8c1c1a in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x55a2ad02e56a in ?? ()
#26 0x7f3bbce23a90 in __libc_start_call_main
(main=main@entry=0x55a2ad02bc40, argc=argc@entry=1,
argv=argv@entry=0x7fff9ca54408) at ../sysdeps/nptl/libc_start_call_main.h:58
#27 0x7f3bbce23b49 in __libc_start_main_impl (main=0x55a2ad02bc40, argc=1,
argv=0x7fff9ca54408, init=, fini=,
rtld_fini=, stack_end=0x7fff9ca543f8) at ../csu/libc-start.c:360
#28 0x55a2ad02ec65 in ?? ()
[Inferior 1 (process 617525) detached]

Reported using DrKonqi

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[kcharselect] [Bug 472376] KCharSelect Missing entire "Mathematical Alphanumeric Symbols" block

[Michael]

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

--- Comment #2 from Michael  ---
Thank you, I tried searching but I didn't realize the technical reason behind
it and couldn't get a match. Looks like it's an old bug, 16 years old.

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

[krita] [Bug 472343] Levels filter layer properties set in Python have no effect on that filter layer

[varkatope]

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

--- Comment #8 from varkatope  ---
(In reply to Deif Lou from comment #7)
> If you have the crash in the nightly that will have my changes then it will
> need a new bug report, but it will have to provide the steps to reproduce
> the issue and maybe the script you use (or a simplified version that also
> provokes the crash) to debug. The safe asserts appear also in the nightly
> that doesn't have my changes so the issue may be other.

Alright, I'll see if it crops up in the next build with your changes. Thanks.

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

[digikam] [Bug 472417] New: Selective Rebuilding of the Face Recognition Training Data

[Craig]

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

Bug ID: 472417
   Summary: Selective Rebuilding of the Face Recognition Training
Data
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Maintenance-Faces
  Assignee: digikam-bugs-n...@kde.org
  Reporter: craigfryer...@gmail.com
  Target Milestone: ---

SUMMARY
***
May be I am uncoordinated, but I seem to have confirmed the wrong face many
times now. I know there is the feature in the maintenance tools to rebuild the
training database. This feature is fine as the database should be retrained
from time to time, however when the database becomes large and only one on face
(person) needs to be retrained, this is a very slow process. For example I have
one person's face that appears over 14,000 times in a set of over 70,000
photographs.

I propose that either the rebuilding could be done for just one person, or an
undo function for Confirmation process could be made available.
***

SOFTWARE/OS VERSIONS
Windows:  10

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[digikam] [Bug 472416] New: Face Recognition- Duplication of a Confirmed Face

[Craig]

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

Bug ID: 472416
   Summary: Face Recognition- Duplication of a Confirmed Face
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Faces-Recognition
  Assignee: digikam-bugs-n...@kde.org
  Reporter: craigfryer...@gmail.com
  Target Milestone: ---

SUMMARY
***
If a face has already been Confirmed in an image it is highly unlikely that the
same face (person) would appear in the same image. This particularly assists
with pictures containing family members that might have similar facial
features, very young children with less distinct features and low resolution
images. If a global option was made available to not suggest the matching of a
face, if that face has already been confirmed in the image, this would reduce
the number of false suggestions.
***

SOFTWARE/OS VERSIONS
Windows:  10

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

[digikam] [Bug 415599] Add date to help DNN face recognition for baby/kid/adult distinction

[Craig]

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

Craig  changed:

   What|Removed |Added

 CC||craigfryer...@gmail.com

--- Comment #3 from Craig  ---
(In reply to Maik Qualmann from comment #1)
> No, a date is not a parameter for facial recognition. What if old children's
> photos are scanned? Then we have a current date with an old photo.
> 
> Maik

Not Before / Not After Date
I think a simplified method could be used to dramatically reduce the rate of
false recognition of faces is to filter the suggestions by the date the photo
was taken. A face would not be recognised if the photo was taken before or
after a set of dates entered into the faces profile. This would avoid faces
being suggested for a person that is no longer alive or before they were born.
The filter dates need not be the date of birth or death as it could simply be
the date before or after which that face would not appear in the pool of faces.

I agree that breaking up the training data by age category sounds helpful, but
other than when a person is a young baby this shouldn't help the AI as the
basic parameters of a face remain fairly similar throughout life.

I understand the issue with photos that have been scanned at a later date,
however scanned images should have their date taken changed to the date when
the original photo was taken. The information on when the photo was scanned can
be tagged or putting into the Meta data in some other way.

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

[kwin] [Bug 471089] Undocumented gestures/mouse swipe

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[krita] [Bug 472248] Jagged edges when rotating objects

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

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

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

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

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

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

[kmymoney] [Bug 442665] Mapping new account to existing bank errors

[Bug Janitor Service]

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

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

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

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

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

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

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

[kwin] [Bug 471054] running into a hard coded limit in workspace_wrapper.h - - - causing kwin crashes

[Bug Janitor Service]

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

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

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

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

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

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

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

[kwin] [Bug 420157] Desktop is unresponsive after ALT+Tabbing

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kio-extras] [Bug 461768] SFTP connection dies while copying over a slow connection

[Bug Janitor Service]

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

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

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

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

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

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

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

[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM

[Tim Richardson]

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

Tim Richardson  changed:

   What|Removed |Added

 CC||t...@tim-richardson.net

--- Comment #40 from Tim Richardson  ---
I'm using kubuntu 23.04 with backports (plasma 5.27.6) . I get this logout hang
with kernel 6.4 (Liquorix) but not with the distro's 6.2 kernel.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[frameworks-plasma] [Bug 472391] Search box's focus/unfocus animation is distracting during widget popup animation

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #6 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/829

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

[dolphin] [Bug 463136] Copying files by dragging them doesn't work. Also dragging files to folders sometimes makes the whole editor freeze for some time.

[Dick Tracey]

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

--- Comment #11 from Dick Tracey  ---
So far, on Arch Linux, this only happens to a dolphin process started for a
different user, using kdesu dbus-launch:

kdesu -u user dbus-launch dolphin

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

[dolphin] [Bug 463136] Copying files by dragging them doesn't work. Also dragging files to folders sometimes makes the whole editor freeze for some time.

[Dick Tracey]

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

--- Comment #10 from Dick Tracey  ---
Happens on Arch Linux with fuse module loaded.

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

[krunner] [Bug 472415] KRunner crashed when I typed =

[bugzilla_noreply]

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

--- Comment #1 from efole...@live.com ---
Created attachment 160403
  --> https://bugs.kde.org/attachment.cgi?id=160403=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[krunner] [Bug 472415] New: KRunner crashed when I typed =

[bugzilla_noreply]

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

Bug ID: 472415
   Summary: KRunner crashed when I typed =
Classification: Plasma
   Product: krunner
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: efole...@live.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

Application: krunner (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-10-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
I was going to use KRunner to calculate the square root of 21 but when I hit
the equal key KRunner crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#4  0x7efd57c55a60 in MathStructure::type() const () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#5  0x7efd57c58b72 in MathStructure::MathStructure(MathStructure const&) ()
from /lib/x86_64-linux-gnu/libqalculate.so.22
#6  0x7efd57bd6bf8 in CalculateThread::run() () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#7  0x7efd57c6596f in Thread::doRun(void*) () from
/lib/x86_64-linux-gnu/libqalculate.so.22
[...]
#11 0x7efdafb0984e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5


Reported using DrKonqi

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

[digikam] [Bug 415777] A tool to remove duplicate faces ?

[Craig]

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

Craig  changed:

   What|Removed |Added

 CC||craigfryer...@gmail.com

--- Comment #4 from Craig  ---
(In reply to Maik Qualmann from comment #3)
> Git commit 7253440154529ab5d986c2869b08b5281639028e by Maik Qualmann.
> Committed on 26/09/2021 at 15:57.
> Pushed by mqualmann into branch 'master'.
> 
> check for existing faces in the database
> when reading face metadata.
> Related: bug 440773, bug 441378
> FIXED-IN: 7.4.0
> 
> M  +2-2NEWS
> M  +37   -11   core/libs/database/item/scanner/itemscanner_photo.cpp
> 
> https://invent.kde.org/graphics/digikam/commit/
> 7253440154529ab5d986c2869b08b5281639028e

I am still seeing this problem in version 8.0.0 (may be 8.0.1) on Windows 10.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[digikam] [Bug 425263] Blur Level on Face Detection

[Craig]

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

Craig  changed:

   What|Removed |Added

 CC||craigfryer...@gmail.com

--- Comment #3 from Craig  ---
I have some suggestions for improvements that encompass this problem.

On a typical set of images the ability to accurately recognise faces declines
as more images are added. The main reason for this is that poor quality images
pollute the reference data that the software uses for the recognition of faces.
Recognised faces that are blurred, out of focus, wearing sunglasses or low
resolution contain information that is too similar to other faces in the pool
of faces to be recognised.

Selective Training Data
One of the best methods to improve the rate of face recognition is to improve
the training data. Instead of having just two categories for faces: Confirmed
and Unconfirmed, an additional category could be added, Reference. In this case
only pictures of a face that are in the Reference category would be used in the
recognition training data. Pictures could be categorised into the Reference
category either manually or automatically. By the manual method good quality
faces across a range of ages and situations (ie wearing glasses) could be
tagged to be used in the Reference training data.

Obviously a large number of reference faces would still be required for the
training data, but in a large album of pictures that won’t be a problem. For
example I have person’s face appearing in over 14,000 images, however many of
these are blurred, out of focus or low resolution. A subset of these images
would still be suitable even if it only contained 10% of the images. In
addition using a smaller training data set would improve the speed of clearing
and rebuilding the training data.

The automatic method could use existing algorithms to exclude “Confirmed” face
pictures that are blurred, low resolution or out of focus from the training
data for that particular face. While an image in totality may not be blurred,
low resolution or out of focus, but the section of the image that includes the
face could be, and thus should be excluded from the training data.

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

[krita] [Bug 472414] Crash when undoing the move tool on a keyframe (git bc41e49)

[Cade Martinez]

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

--- Comment #2 from Cade Martinez  ---
Created attachment 160402
  --> https://bugs.kde.org/attachment.cgi?id=160402=edit
Video demonstration of steps to reproduce

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

[krita] [Bug 472414] Crash when undoing the move tool on a keyframe (git bc41e49)

[Cade Martinez]

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

--- Comment #1 from Cade Martinez  ---
Created attachment 160401
  --> https://bugs.kde.org/attachment.cgi?id=160401=edit
Crash log

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

[krita] [Bug 472414] New: Crash when undoing the move tool on a keyframe (git bc41e49)

[Cade Martinez]

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

Bug ID: 472414
   Summary: Crash when undoing the move tool on a keyframe (git
bc41e49)
Classification: Applications
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: know.one.will.find@gmail.com
  Target Milestone: ---

Created attachment 160400
  --> https://bugs.kde.org/attachment.cgi?id=160400=edit
Krita system information

SUMMARY
Drawing on any animation frame and then using the "Move a layer" tool (in a
particular order) will crash when undone.
Affects Krita 5.1.5 and Krita 5.2.0-prealpha (git bc41e49).

STEPS TO REPRODUCE
1. Open or create any document with a paint layer. (A layer with existing
frames is ok)
2. Draw anything on the paint layer. (A dot or line is ok)
3. Create new keyframe and draw
5. Go back to previous keyframe and draw
6. Use the "Move a layer" tool (T) to move the current drawing
7. Undo everything
(Video demonstration attached)

OBSERVED RESULT
Krita abruptly crashes with the same access violation. (Full crash log
attached)
"
Access Violation at location 7FFDF2599EEB in module libkritaimage.dll
Writing to location 0088
  libkritaimage.dll!KisPaintDevice::Private::invalidateFrameCache+0x2b
  libkritaimage.dll!KisTransactionData::undo+0x1bf
"

EXPECTED RESULT
All the "steps to reproduce" are undone.

SOFTWARE/OS VERSIONS
Windows: 10 (Version 21H2)
Qt Version: 5.15.7

ADDITIONAL INFORMATION
- This bug affects both Krita 5.1.5, Krita 5.2.0-prealpha (git bc41e49),
- Video demonstration, crash log, and version info are attached

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

[konsole] [Bug 472413] New: Font mangled after returning laptop to docking station. (internal and external monitors both HiDPI)

[Thomas Cherryhomes]

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

Bug ID: 472413
   Summary: Font mangled after returning laptop to docking
station. (internal and external monitors both HiDPI)
Classification: Applications
   Product: konsole
   Version: 23.04.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: thom.cherryho...@gmail.com
  Target Milestone: ---

Created attachment 160399
  --> https://bugs.kde.org/attachment.cgi?id=160399=edit
Snapshot of Konsole window.

SUMMARY
***
Thinkpad P17 Gen1 laptop with Optimus managed GPU (Hybrid mode) is running an
internal LCD at 3840x2160. 
Docking station is running two LG 27UPD88 monitors (left one portrait, right
one landscape and primary) via Thunderbolt docking station.
Konsole font got mangled when dragging window from right display to the left
display, as seen in attachment.
***

STEPS TO REPRODUCE
1. Unplug laptop from docking station.
2. Use laptop on battery for an hour and a half.
3. Plug back into docking station.

OBSERVED RESULT

Mangled fonts.

EXPECTED RESULT

Not mangled fonts.

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

ADDITIONAL INFORMATION

GPU: Intel UHD P630 GPU and NVIDIA Quadro RTX 3000

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

[frameworks-kservice] [Bug 472345] Crash on launch in KSycocaEntry::name() on first logon to Plasma6

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Crash on launch on first|Crash on launch in
   |logon to Plasma6|KSycocaEntry::name() on
   ||first logon to Plasma6
 Resolution|--- |WAITINGFORINFO
  Component|general |general
 Status|REPORTED|NEEDSINFO
   Assignee|plasma-b...@kde.org |fa...@kde.org
Product|Welcome Center  |frameworks-kservice
 CC||alexander.loh...@gmx.de,
   ||kdelibs-b...@kde.org

--- Comment #1 from Nate Graham  ---
Being in ApplicationInfo::setDesktopName() makes me think there's a malformed
desktop file somewhere that's making the app crash in kservice when it tries to
read it.

Can you go into frame 11 and print desktopName?

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[plasmashell] [Bug 472412] New: plasmashell sometimes crashes in PlasmaQuick::Dialog::event() clicking on open apps in the Task Manager to switch to them

[Nate Graham]

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

Bug ID: 472412
   Summary: plasmashell sometimes crashes in
PlasmaQuick::Dialog::event() clicking on open apps in
the Task Manager to switch to them
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: crash
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
  Target Milestone: 1.0

STEPS TO REPRODUCE
1. Open an app
2. Click on its Task manager icon


OBSERVED RESULT
Sometimes (like, 5% of the time), plasmashell crashes with a backtrace like
this:

#0  __pthread_kill_implementation
(threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at
pthread_kill.c:44
#1  0x7f68514b08b3 in __pthread_kill_internal (signo=11,
threadid=)
at pthread_kill.c:78
#2  0x7f685145fabe in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x7f6854b30916 in KCrash::defaultCrashHandler(int) (sig=11)
at /home/nate/kde/src/kcrash/src/kcrash.cpp:616
#4  0x7f685145fb70 in  () at /lib64/libc.so.6
#5  __pthread_kill_implementation
(threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at
pthread_kill.c:44
#6  0x7f68514b08b3 in __pthread_kill_internal (signo=11,
threadid=)
at pthread_kill.c:78
#7  0x7f685145fabe in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#8  0x7f685145fb70 in  () at /lib64/libc.so.6
#9  0x7f68514ab1d7 in __futex_abstimed_wait_common64
(private=0, cancel=true, abstime=0x0, op=393, expected=0,
futex_word=0x3c1bd34)
at futex-internal.c:57
#10 __futex_abstimed_wait_common
(futex_word=futex_word@entry=0x3c1bd34, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0,
cancel=cancel@entry=true) at futex-internal.c:87
#11 0x7f68514ab25f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x3c1bd34, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#12 0x7f68514adb79 in __pthread_cond_wait_common
(abstime=0x0, clockid=0, mutex=, cond=0x3c1bd08) at
pthread_cond_wait.c:503
#13 ___pthread_cond_wait (cond=0x3c1bd08, mutex=) at
pthread_cond_wait.c:618
#14 0x7f6851d0b1ab in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x3c1bce0)
at
/usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:87
#15 QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x52d6638, deadline=...)
at
/usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:160
#16 0x7f68544c53ab in
QSGThreadedRenderLoop::handleObscurity(QSGThreadedRenderLoop::Window*)
(this=this@entry=0x16382c0, w=0x25eceb8)
at
/usr/src/debug/qt6-qtdeclarative-6.5.1-1.fc38.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1323
#17 0x7f68544c6176 in QSGThreadedRenderLoop::hide(QQuickWindow*)
(this=0x16382c0, window=0x1ddf6d0)
at
/usr/src/debug/qt6-qtdeclarative-6.5.1-1.fc38.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1116
#18 0x7f6852460438 in QWindow::event(QEvent*) (this=0x1ddf6d0,
ev=0x7ffce0aca2f0, 
ev@entry=0xd2bb60)
at
/usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/gui/kernel/qwindow.cpp:2523
#19 0x7f68542e77a0 in QQuickWindow::event(QEvent*)
(this=this@entry=0x1ddf6d0, event=0xd2bb60, 
event@entry=0x7ffce0aca2f0)
at
/usr/src/debug/qt6-qtdeclarative-6.5.1-1.fc38.x86_64/src/quick/items/qquickwindow.cpp:1570
#20 0x7f685543f83d in PlasmaQuick::Dialog::event(QEvent*)
(this=this@entry=0x1ddf6d0, event=event@entry=0x7ffce0aca2f0)
at /home/nate/kde/src/plasma-framework/src/plasmaquick/dialog.cpp:1596
#21 0x7f682ffd3645 in ToolTipDialog::event(QEvent*) (this=0x1ddf6d0,
e=0x7ffce0aca2f0)
at
/home/nate/kde/src/plasma-framework/src/declarativeimports/core/tooltipdialog.cpp:88
#22 0x7f68531c0b08 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x1ddf6d0, e=0x7ffce0aca2f0)
at
/usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/widgets/kernel/qapplication.cpp:3287
#23 0x7f6851b7c308 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x1ddf6d0, event=0x7ffce0aca2f0)
at
/usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/corelib/kernel/qcoreapplication.cpp:1115
#24 0x7f6851b7c50d in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/corelib/kernel/qcoreapplication.cpp:1533
#25 0x7f685245d721 in QWindowPrivate::setVisible(bool) (visible=false,
this=)
at
/usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/gui/kernel/qwindow.cpp:397
#26 QWindow::setVisible(bool) (this=, 

[kcalc] [Bug 472411] New: Binary data hidden

[bugzilla_noreply]

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

Bug ID: 472411
   Summary: Binary data hidden
Classification: Applications
   Product: kcalc
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ete...@alum.rit.edu
  Reporter: neumann6...@gmail.com
  Target Milestone: ---

Created attachment 160398
  --> https://bugs.kde.org/attachment.cgi?id=160398=edit
The binary hides the data

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
Open up Kalc use complex calc

OBSERVED RESULT
Hides binary 

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.

[systemsettings] [Bug 471942] If the Touchpad KCM is open via Kickoff or Krunner, the "Apply" button remains greyed out after a change

[Jakob Petsovits]

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

Jakob Petsovits  changed:

   What|Removed |Added

 CC||j.acco...@petsovits.com

--- Comment #3 from Jakob Petsovits  ---
Possibly related, the header caption ("Touchpad" in the toolbar area) also
doesn't show when opened with KRunner. Switching to another KCM and back makes
everything work.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[choqok] [Bug 472380] Choqok hasn't updated my Twitter timeline for 8 days now

[David]

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

--- Comment #2 from David  ---
On 7/19/23 00:36, Tobias Fella wrote:
> https://bugs.kde.org/show_bug.cgi?id=472380
>
> Tobias Fella  changed:
>
> What|Removed |Added
> 
>   Status|REPORTED|RESOLVED
>   Resolution|--- |UPSTREAM
>   CC||fe...@posteo.de
>
> --- Comment #1 from Tobias Fella  ---
> Yes, there's nothing we can do about that
>
Thanks, that's what I thought. Will remove my Twitter account from Choqok.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[Spectacle] [Bug 472410] New: Feature Request: Allow clicking a window to capture it in "Rectangular Region" selection mode

[Lea]

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

Bug ID: 472410
   Summary: Feature Request: Allow clicking a window to capture it
in "Rectangular Region" selection mode
Classification: Applications
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: m...@lea.moe
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
Currently "Rectangular Region" and "Window Under Cursor" are separate selection
modes, however the behavior of the latter mode could be applied to region
selection mode with a setting and cli argument (or maybe even by default). 
With this enabled, clicking a window would capture it with the applied edits –
matching the functionality of similar software.

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

[korganizer] [Bug 470584] KOrganizer crash while changing filter in ToDo List

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/pim/
   ||eventviews/-/commit/6984c3b
   ||8752956e55971b75a501fce395c
   ||5284d7
   Version Fixed In||23.08
 Status|ASSIGNED|RESOLVED

--- Comment #4 from Allen Winter  ---
Git commit 6984c3b8752956e55971b75a501fce395c5284d7 by Allen Winter.
Committed on 19/07/2023 at 19:50.
Pushed by winterz into branch 'release/23.04'.

Avoid crashes if findCalendar or calendar2 return empty
FIXED-IN: 23.08

M  +43   -22   src/agenda/agendaview.cpp

https://invent.kde.org/pim/eventviews/-/commit/6984c3b8752956e55971b75a501fce395c5284d7

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

[valgrind] [Bug 472409] Assertion '!overlap' failed.

[psykose]

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

psykose  changed:

   What|Removed |Added

 CC||al...@ayaya.dev

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

[krita] [Bug 472343] Levels filter layer properties set in Python have no effect on that filter layer

[Deif Lou]

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

--- Comment #7 from Deif Lou  ---
If you have the crash in the nightly that will have my changes then it will
need a new bug report, but it will have to provide the steps to reproduce the
issue and maybe the script you use (or a simplified version that also provokes
the crash) to debug. The safe asserts appear also in the nightly that doesn't
have my changes so the issue may be other.

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

[valgrind] [Bug 472402] memcheck "make tests" build fails: filter_sized_delete missing

[John Reiser]

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

--- Comment #4 from John Reiser  ---
(In reply to John Reiser from comment #3)
> The problem no longer appears in:
>commit cb684b50e7d4d845b56abea72fd9b9925fed644e (HEAD -> master,
> origin/master, origin/HEAD)
>Date:   Mon May 22 19:49:08 2023 +0200
> after explicit "./autogen.sh" before "make -j4".
> 
> I did not expect that running autogen.sh would be required after "git pull".
> This seems peculiar.

The full sequence of the "fix" was:  "git pull; ./autogen.sh; ./configure; make
-j4".

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

[valgrind] [Bug 472402] memcheck "make tests" build fails: filter_sized_delete missing

[John Reiser]

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

--- Comment #3 from John Reiser  ---
The problem no longer appears in:
   commit cb684b50e7d4d845b56abea72fd9b9925fed644e (HEAD -> master,
origin/master, origin/HEAD)
   Date:   Mon May 22 19:49:08 2023 +0200
after explicit "./autogen.sh" before "make -j4".

I did not expect that running autogen.sh would be required after "git pull". 
This seems peculiar.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[dolphin] [Bug 469324] Cuted files/folders still listed

[mozo]

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

mozo  changed:

   What|Removed |Added

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

--- Comment #23 from mozo  ---
For some reason I have holded Dolphin updates. With the latest Dolphin version
there's no problem, thank you. There is actually one more related problem but I
will use another icon to open Dolphin.

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

[valgrind] [Bug 472409] New: Assertion '!overlap' failed.

[Stefan de Konink]

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

Bug ID: 472409
   Summary: Assertion '!overlap' failed.
Classification: Developer tools
   Product: valgrind
   Version: 3.21.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: ste...@konink.de
  Target Milestone: ---

SUMMARY
Valgrind on Alpine Linux debugging a Qt6 application gave me several issues.
The first issue was already resolved in git a few days ago
(453c733ce9dc5dce043e03b7b58efdbf46cd). This has been patched today in
Alpine Linux.

I end up with the trace below.


STEPS TO REPRODUCE
1.  valgrind --tool=none --track-fds=yes ./myapp

OBSERVED RESULT

==2489== Nulgrind, the minimal Valgrind tool
==2489== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote.
==2489== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==2489== Command: ./myapp -platform xcb
==2489== 
==2491== 
==2491== FILE DESCRIPTORS: 3 open (3 std) at exit.
==2491== 

valgrind: m_debuginfo/debuginfo.c:914 (truncate_DebugInfoMapping_overlaps):
Assertion '!overlap' failed.

host stacktrace:
==2489==at 0x5801C37D: show_sched_status_wrk (m_libcassert.c:406)
==2489==by 0x5801C5D9: report_and_quit (m_libcassert.c:477)
==2489==by 0x5801C7AA: vgPlain_assert_fail (m_libcassert.c:543)
==2489==by 0x5803323E: vgPlain_di_notify_mmap (debuginfo.c:1151)
==2489==by 0x580598A2: vgModuleLocal_generic_PRE_sys_mmap
(syswrap-generic.c:2465)
==2489==by 0x58010329: vgSysWrap_amd64_linux_sys_mmap_before
(syswrap-amd64-linux.c:413)
==2489==by 0x5800EF24: vgPlain_client_syscall (syswrap-main.c:2240)
==2489==by 0x5800B88E: handle_syscall (scheduler.c:1206)
==2489==by 0x5800E0B6: vgPlain_scheduler (scheduler.c:1552)
==2489==by 0x58062ADE: run_a_thread_NORETURN (syswrap-linux.c:102)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable syscall 9 (lwpid 2489)
==2489==at 0x4035244: mmap (syscall_arch.h:61)
==2489==by 0x4059E37: map_library (dynlink.c:646)
==2489==by 0x405A667: load_library (dynlink.c:1181)
==2489==by 0x405BA53: dlopen (dynlink.c:2163)
==2489==by 0x59A53A2: ??? (in /usr/lib/libQt6Core.so.6.5.1)
==2489==by 0x59A61C1: ??? (in /usr/lib/libQt6Core.so.6.5.1)
==2489==by 0x59A6417: ??? (in /usr/lib/libQt6Core.so.6.5.1)
==2489==by 0x5824A2F: QFactoryLoader::instance(int) const (in
/usr/lib/libQt6Core.so.6.5.1)
==2489==by 0x4FB09E3: ??? (in /usr/lib/libQt6Gui.so.6.5.1)
==2489==by 0x4FB4E51: QImageWriter::supportedImageFormats() (in
/usr/lib/libQt6Gui.so.6.5.1)
==2489==by 0x13C65098: ??? (in
/usr/lib/qt6/plugins/multimedia/libffmpegmediaplugin.so)
==2489==by 0x13C6A179: ??? (in
/usr/lib/qt6/plugins/multimedia/libffmpegmediaplugin.so)
==2489==by 0x97FE0D9: QPlatformMediaIntegration::instance() (in
/usr/lib/libQt6Multimedia.so.6.5.1)
==2489==by 0x9813EDE: QVideoSink::QVideoSink(QObject*) (in
/usr/lib/libQt6Multimedia.so.6.5.1)
==2489==by 0x97857CE: QQuickVideoOutput::QQuickVideoOutput(QQuickItem*) (in
/usr/lib/libQt6MultimediaQuick.so.6.5.1)
==2489==by 0x978FA6B: ??? (in /usr/lib/libQt6MultimediaQuick.so.6.5.1)
==2489==by 0x4C3DFFB: QQmlType::create(void**, unsigned long) const (in
/usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4C3E0AB: QQmlType::createWithQQmlData() const (in
/usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4BFEEFA: QQmlObjectCreator::createInstance(int, QObject*,
bool) (in /usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4C006B4:
QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*,
QV4::CompiledData::Binding const*) (in /usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4C02B5E:
QQmlObjectCreator::setupBindings(QFlags) (in
/usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4C0A262: QQmlObjectCreator::populateInstance(int, QObject*,
QObject*, QQmlPropertyData const*, QV4::CompiledData::Binding const*) (in
/usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4BFEA4B: QQmlObjectCreator::createInstance(int, QObject*,
bool) (in /usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4BFB424: QQmlObjectCreator::create(int, QObject*,
QQmlInstantiationInterrupt*, int) (in /usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4BFE84E: QQmlObjectCreator::createInstance(int, QObject*,
bool) (in /usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4C006B4:
QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*,
QV4::CompiledData::Binding const*) (in /usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4C02B5E:
QQmlObjectCreator::setupBindings(QFlags) (in
/usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4C0A262: QQmlObjectCreator::populateInstance(int, QObject*,
QObject*, QQmlPropertyData const*, QV4::CompiledData::Binding const*) (in
/usr/lib/libQt6Qml.so.6.5.1)
==2489==by 0x4BFEA4B: QQmlObjectCreator::createInstance(int, QObject*,
bool) (in /usr/lib/libQt6Qml.so.6.5.1)
==2489==by 

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[systemsettings] [Bug 457041] Can't save Wireguard VPN settings

[Dashon]

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

--- Comment #2 from Dashon  ---
I've been running into this myself:

Operating System: EndeavourOS 
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.3-zen1-2-zen (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C95
System Version: 1.0

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

[systemsettings] [Bug 457041] Can't save Wireguard VPN settings

[Dashon]

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

Dashon  changed:

   What|Removed |Added

 CC||sparky123558w...@gmail.com

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

[kio-extras] [Bug 296526] Dolphin is too slow when upload a file on a SSH server

[Andrej Halveland]

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

Andrej Halveland  changed:

   What|Removed |Added

 CC||andrej.h...@gmail.com

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist

[Josh]

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

Josh  changed:

   What|Removed |Added

 CC||kde.isolating...@8shield.ne
   ||t

--- Comment #20 from Josh  ---
I agree that this should be optional. It feels unintuitive and more like a bug
than a feature.

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

[kdenlive] [Bug 472408] New: Feature Request: Add button to switch between sequence in Menubar and addressed it in "Find Action..." and "Configure Keyboard Shortcuts".

[Mat.]

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

Bug ID: 472408
   Summary: Feature Request: Add button to switch between sequence
in Menubar and addressed it in "Find Action..." and
"Configure Keyboard Shortcuts".
Classification: Applications
   Product: kdenlive
   Version: 23.04.2
  Platform: Microsoft Windows
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: master.lee...@gmail.com
  Target Milestone: ---

SUMMARY

Feature Request: Add button to switch between sequence in Menubar and addressed
it in "Find Action..." and "Configure Keyboard Shortcuts".

OBSERVED RESULT

Since the Nested Timeline feature was added, what it was really cool, I suppose
the developers forgot the add the command that you can perform in "Menubar" and
in "Find Action..." to switch between the sequences open.

For this moment, althought it isn't index in Configure Keyobard Shortcuts", it
is possible to use the keyboard shortcut "Ctrl + Tab" and "Ctrl + Shift + Tab"
to switch to next and previous open sequence, respectively.

EXPECTED RESULT

Add submenu in Menubar with the item:

Timeline
Nested Timeline
Switch to Next Sequence Ctrl + Tab
Switch to Previous Sequence Ctrl + Tab

Index to the "Configure Keyboard Shortcut" the keyboard shortcut to switch to
next and previous sequence.

Also index the button to switch to next or previous sequence in "Find
Action...".

SOFTWARE/OS VERSIONS
Windows: Windows 10 Version 2009 (x86_64)
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.9 (built against 5.15.9)

ADDITIONAL INFORMATION
The structure of the Nested Timeline in Menubar is a just a example.

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

[kdeconnect] [Bug 467424] Android Mouse Receiver or Remote Control function can not be disabled on laptop via touchpad

[korbel]

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

korbel  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||korbe...@gmail.com

--- Comment #1 from korbel  ---


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

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

[kdeconnect] [Bug 442169] Unlocking remote control inputs on the desktop app requires pressing left and right mouse buttons at the same time which is impossible on many devices without a mouse

[korbel]

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

korbel  changed:

   What|Removed |Added

 CC||tarakbu...@gmail.com

--- Comment #1 from korbel  ---
*** Bug 467424 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 472343] Levels filter layer properties set in Python have no effect on that filter layer

[varkatope]

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

--- Comment #6 from varkatope  ---
(In reply to Deif Lou from comment #4)
> Hi. Can you tell when this happens? For some specific type of layer or the
> like? I think that may be some unrelated bug to this and may need another
> bug report.

Hi again.

Unfortunately I can`t really tell at what point I`m getting that error in your
build. If I just start a new project and start adding layers, filers, etc. I
can`t recreate it. Only when my plugin adds a bunch of stuff in quick
succession, makes groups, locks layers, selects stuff by name... I don`t know.
The new nightly (529349f) seems to work fine for me and I thnk that
includes changes to "flake" specifically as in here:
https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/2072/changes

Here are a few logs but not sure they`re super helpful. Let me know if you
think I should do a separate bug report on this, though.

Thanks.

Your build:
SESSION: 19 Jul 2023 14:48:16 -0400. Executing
/tmp/.mount_krita-mmfdXP/usr/bin/krita

Krita Version: 5.2.0-prealpha (git f742174), Qt version compiled: 5.15.7,
loaded: 5.15.7. Process ID: 33666
-- -- -- -- -- -- -- --
19 Jul 2023 14:48:16 -0400: Style: fusion. Available styles: Windows, Fusion
19 Jul 2023 14:48:18 -0400: Database is up to date. Version: 0.0.17, created by
Krita 5.1.0, at Wed. Sep. 7 22:50:11 2022
19 Jul 2023 14:48:18 -0400: Could not load resource
layerstyles/normals_tools_library.asl
19 Jul 2023 14:48:18 -0400: Could not load resource layerstyles/normals.tag
19 Jul 2023 14:48:18 -0400: Could not load resource
layerstyles/small_recessed_grille.asl
19 Jul 2023 14:48:24 -0400: KisAppimageUpdater: update check finished. Result:
2 Exit status: 0
path:
/home/myname/Desktop/Krita_levels/krita-5.2.0-prealpha-f742174ed7-x86_64.appimage
output: 
19 Jul 2023 14:48:31 -0400: Created image "Project Name", 1024 * 1024 pixels,
300 dpi. Color model: 16-bit integer/channel RGB/Alpha
(sRGB-elle-V2-srgbtrc.icc). Layers: 1
19 Jul 2023 14:48:33 -0400: SAFE ASSERT (krita): "dummy" in file
/builds/graphics/krita/libs/ui/flake/kis_dummies_facade_base.cpp, line 120

KRITA DID NOT CLOSE CORRECTLY


The new nightly (which doesn`t include your changes yet):

SESSION: 19 Jul 2023 15:07:30 -0400. Executing
/tmp/.mount_krita-eAhhMB/usr/bin/krita

Krita Version: 5.2.0-prealpha (git 529349f), Qt version compiled: 5.15.7,
loaded: 5.15.7. Process ID: 34157
-- -- -- -- -- -- -- --
19 Jul 2023 15:07:30 -0400: Style: fusion. Available styles: Windows, Fusion
19 Jul 2023 15:07:32 -0400: Database is up to date. Version: 0.0.17, created by
Krita 5.1.0, at Wed. Sep. 7 22:50:11 2022
19 Jul 2023 15:07:32 -0400: Could not load resource
layerstyles/normals_tools_library.asl
19 Jul 2023 15:07:32 -0400: Could not load resource layerstyles/normals.tag
19 Jul 2023 15:07:32 -0400: Could not load resource
layerstyles/small_recessed_grille.asl
19 Jul 2023 15:07:37 -0400: KisAppimageUpdater: update check finished. Result:
0 Exit status: 0
path: /home/myname/Downloads/krita-5.2.0-prealpha-529349f772-x86_64.appimage
output: 
19 Jul 2023 15:07:45 -0400: Created image "Project Name", 1024 * 1024 pixels,
300 dpi. Color model: 16-bit integer/channel RGB/Alpha
(sRGB-elle-V2-srgbtrc.icc). Layers: 1
19 Jul 2023 15:07:46 -0400: SAFE ASSERT (krita): "dummy" in file
/home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/ui/flake/kis_dummies_facade_base.cpp,
line 120
19 Jul 2023 15:07:46 -0400: SAFE ASSERT (krita): "dummy" in file
/home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/ui/flake/kis_dummies_facade_base.cpp,
line 120

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[kwin] [Bug 472407] Walyand: Screencasting causes KWin to take up 100% of a single CPU core

[Naxdy]

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

--- Comment #1 from Naxdy  ---
Also, possibly related to: https://bugs.kde.org/show_bug.cgi?id=467574

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

[kwin] [Bug 472407] Walyand: Screencasting causes KWin to take up 100% of a single CPU core

[Naxdy]

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

Naxdy  changed:

   What|Removed |Added

   Keywords||regression, wayland

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

[kwin] [Bug 472407] New: Walyand: Screencasting causes KWin to take up 100% of a single CPU core

[Naxdy]

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

Bug ID: 472407
   Summary: Walyand: Screencasting causes KWin to take up 100% of
a single CPU core
Classification: Plasma
   Product: kwin
   Version: 5.27.6
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: xna...@hydra-development.net
  Target Milestone: ---

SUMMARY
The commit
https://invent.kde.org/plasma/kwin/-/commit/23806d31e23d2ef2bc8344114feb6d27364cdc01
has introduced a regression that can be observed on my system that manifests
itself as KWin taking up 100% of a single CPU core (and dropping frames) when
screencasting.

Reverting the mentioned commit has completely resolved the issue for me.

STEPS TO REPRODUCE
0. Log in to Plasma Wayland session
1. Begin screencasting (I used rectangular region which is scheduled for 6.0,
but fullscreen produced the same issue for me - I used OBS to test this)

OBSERVED RESULT
KWin takes up 100% of a singe CPU core (thread), mouse movement is choppy, and
journalctl --user shows KWin is struggling with frame drops.

EXPECTED RESULT
Screencasting is smooth, does not impact desktop usage, and does not take 100%
of a single CPU core.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS
(available in About System)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
-

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

[gwenview] [Bug 452477] Gwenview doesn't open HEIC files

[Alexander Wilms]

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

--- Comment #2 from Alexander Wilms  ---
I encountered the same issue on openSUSE Tumbleweed. Installing libheif1 from
Packman fixed the issue for me:
https://bugzilla.suse.com/show_bug.cgi?id=1213371

Could Dolphin & Gwenview show a button to install the necessary package for
various distros through PackageKit? Since the format is patent-encumbered, this
might affect quite a few distros.

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

[Powerdevil] [Bug 452492] external screen brightness is not restored after wakeup

[Matej Mrenica]

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

Matej Mrenica  changed:

   What|Removed |Added

 CC||matejm98m...@gmail.com

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

[systemsettings] [Bug 472406] New: System settings application won't start

[Oded Arbel]

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

Bug ID: 472406
   Summary: System settings application won't start
Classification: Applications
   Product: systemsettings
   Version: 5.27.6
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: o...@geek.co.il
  Target Milestone: ---

SUMMARY

When trying to launch systemsettings, through the menu, or from the command
line, it does not actually start - no window appears. Other ways to launch the
system settings app also fail - such as running "About this system" from the
main menu, pressing the "settings" icon in the audio mixer panel widget, trying
to start a specific KCM through the main menu, etc.

STEPS TO REPRODUCE
1. In the terminal type `systemsettings5` and ENTER

OBSERVED RESULT
Nothing happens - no window, no output, the prompt reappears almost immediately

EXPECTED RESULT
The system settings application window should appear.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.2.0-25-generic (64-bit)

ADDITIONAL INFORMATION
Looking at the journal, I can see this output:

---8<---
plasmashell[2236669]: kf.kio.gui: Starting process: ("/usr/bin/systemsettings")
plasmashell[2236669]: QString::arg: 2 argument(s) missing in systemsettings
plasmashell[2236669]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286:
Unable to assign [undefined] to QString
plasmashell[2236669]: kf.kio.gui: Setting PID 3931497 for: "systemsettings"
plasmashell[2236669]: kf.kio.gui: Successfully registered new cgroup:
"app-systemsettings-768651f4313d42d5aaa74014fcde1ec1.scope"
plasmashell[2236669]: kf.kio.gui: "systemsettings" exitCode= 0 exitStatus=
QProcess::NormalExit
---8<---

Calling KCMs directly with kcmshell5 seems to work fine - the only KCM that
won't for me is `kcm_hotkeys`, kcmshell5 shows the following errors for it:

---8<---
kf.coreaddons: plugin metadata in "kcm_hotkeys" does not have a valid
'MetaData' object
kf.coreaddons: Checking for plugins in ("/usr/bin/plasma/kcms",
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms")
kf.coreaddons: Checking for plugins in ("/usr/bin/plasma/kcms/systemsettings",
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings")
kf.coreaddons: Checking for plugins in
("/usr/bin/plasma/kcms/systemsettings_qwidgets",
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings_qwidgets")
kf.coreaddons: Checking for plugins in ("/usr/bin/plasma/kcms/kinfocenter",
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/kinfocenter")
kf.service.sycoca: Opening ksycoca from
"/home/odeda/.cache/ksycoca5_en_yTnWV7rpTQzDQ5gELcxORrn78xc="
Could not find module 'kcm_hotkeys'. See kcmshell5 --list for the full list of
modules.
---8<---

Even though kcm_hotkeys does appear in the output of kcmshell5 --list.

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

[Tokodon] [Bug 468949] Loses logins constantly

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

   Version Fixed In||23.08
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #4 from Joshua Goins  ---
We fixed a lot of config bugs, and did a complete overhaul of how account
logins are stored in 23.08 (it was too big to appear in a 23.04 bugfix,
unfortunately .) The release won't appear until next month, but please re-open
if you see this same issue then on Flatpak. Thanks!

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

[Tokodon] [Bug 466573] Accessibility: Keyboard Navigation is a bit buggy under Settings

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[Tokodon] [Bug 470703] The settings cannot be opened on android

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||23.08
 Resolution|--- |FIXED

--- Comment #1 from Joshua Goins  ---
Will be fixed in 23.08, sorry I forgot to backport this to 23.04... I'm not
sure they're tagging another minor release.

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

[kmail2] [Bug 394784] KMAIl 5.8.1: Reply to HTML-mail in text mode includes content from last mail

[Axel Braun]

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

--- Comment #16 from Axel Braun  ---
I think so, I cant reproduce either!

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

[Tokodon] [Bug 472033] Wrong icons

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||23.08
 Resolution|--- |FIXED

--- Comment #1 from Joshua Goins  ---
This will be fixed in 23.08, and it should use the correct icons by default on
other desktop environments like Cinnamon :-)

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

[Tokodon] [Bug 467724] Feature: allow refreshing an open toot

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[Tokodon] [Bug 468814] New Toot button is replicated when viewing a Thread

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||23.08

--- Comment #1 from Joshua Goins  ---
This should be fixed in 23.08 since we now use a single column, and the button
isn't on the thread page anymore.

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

[Tokodon] [Bug 468710] Feature request: Popular post in instance and federation

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

   Version Fixed In||23.08
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Joshua Goins  ---
The Explore tab has been added in 23.08, releasing next month :-)

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

[Tokodon] [Bug 467617] Application freezes after media playback

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||23.08
 Status|ASSIGNED|RESOLVED

--- Comment #16 from Joshua Goins  ---
This will be fixed in 23.08 as we move from GStreamer to MPV :-)

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

[Tokodon] [Bug 471138] Search results' list still being shown after the result is chosen

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[okular] [Bug 472356] Okular crashes when configuring certificates with SafeNet Client

[Ovidiu D . Niţan]

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

--- Comment #5 from Ovidiu D. Niţan  ---
I'm on X11. I'm not using anything fancy, except that my display runs at 120Hz
and my GPU is an AMD Radeon Mobile series.

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

[extra-cmake-modules] [Bug 472361] Allow KDEGitCommitHooks to work with external commit hooks

[Alexander Lohnau]

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

Alexander Lohnau  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
   Version Fixed In||5.109
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/extra-cmake-modules/
   ||-/commit/072f57dbb641caa793
   ||cbcf359091439fe0dccef4

--- Comment #4 from Alexander Lohnau  ---
Git commit 072f57dbb641caa793cbcf359091439fe0dccef4 by Alexander Lohnau.
Committed on 19/07/2023 at 15:33.
Pushed by alex into branch 'master'.

KDEGitCommitHooks: Allow passing in of custom scripts

In case of kphotoalbum, the maintainer wants the clang-format hook in
addition to a set of custom hooks. While we currently append to the file
in case it exists, it would still mean that custom hooks have to be
installed/configured separately.

Because developers can not specify custom hooks, we can just override
the file which will make the entire generation process easier.
Since this is a small behavior change, it is put in a version guard.
FIXED-IN: 5.109

M  +39   -29   kde-modules/KDEGitCommitHooks.cmake
M  +1-1kde-modules/kde-git-commit-hooks/pre-commit.in

https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/072f57dbb641caa793cbcf359091439fe0dccef4

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[krita] [Bug 472343] Levels filter layer properties set in Python have no effect on that filter layer

[Deif Lou]

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

Deif Lou  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/-/commit/929d259
   ||bd4696002b32fad0d1e00f7e184
   ||8a85e7
 Status|ASSIGNED|RESOLVED

--- Comment #5 from Deif Lou  ---
Git commit 929d259bd4696002b32fad0d1e00f7e1848a85e7 by Deif Lou.
Committed on 19/07/2023 at 17:23.
Pushed by merge-service into branch 'master'.

Fix handling of configuration properties on levels filter

Part-of: 

M  +18   -3libs/image/KisLevelsCurve.cpp
M  +5-0libs/image/KisLevelsCurve.h
M  +146  -63   plugins/filters/levelfilter/KisLevelsFilterConfiguration.cpp
M  +12   -10   plugins/filters/levelfilter/KisLevelsFilterConfiguration.h

https://invent.kde.org/graphics/krita/-/commit/929d259bd4696002b32fad0d1e00f7e1848a85e7

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

[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations

[Ilgaz Öcal]

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

Ilgaz Öcal  changed:

   What|Removed |Added

 CC||il...@ilgaz.gen.tr

--- Comment #21 from Ilgaz Öcal  ---
There are thousands of the following error messages on system log. I also saw
signond occupying 100% of a single core for a long time after system came back
from sleep.

ul 19 20:12:30 mbt signonpluginprocess[13235]: Operation requested while plugin
busy! - code 14
Jul 19 20:12:30 mbt kioslave5[3355]: "Failed to I/O session data to/from the
signon daemon."
Jul 19 20:12:30 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Failed to I/O session data to/from the signon daemon."
Jul 19 20:12:30 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:30 mbt kioslave5[3355]: "Casting SessionData into subclass
failed."
Jul 19 20:12:30 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Casting SessionData into subclass failed."
Jul 19 20:12:30 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:31 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:31 mbt signond[12050]: signonsessioncore.cpp 397 replyError
Deprecated error code: 2
Jul 19 20:12:31 mbt signonpluginprocess[13242]: Operation requested while
plugin busy! - code 14
Jul 19 20:12:31 mbt kioslave5[3355]: "Failed to I/O session data to/from the
signon daemon."
Jul 19 20:12:31 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Failed to I/O session data to/from the signon daemon."
Jul 19 20:12:31 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:31 mbt kioslave5[3355]: "Casting SessionData into subclass
failed."
Jul 19 20:12:31 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Casting SessionData into subclass failed."
Jul 19 20:12:31 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:31 mbt signond[12050]: signonsessioncore.cpp 397 replyError
Deprecated error code: 2
Jul 19 20:12:31 mbt signonpluginprocess[13249]: Operation requested while
plugin busy! - code 14
Jul 19 20:12:31 mbt kioslave5[3355]: "Failed to I/O session data to/from the
signon daemon."
Jul 19 20:12:31 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Failed to I/O session data to/from the signon daemon."
Jul 19 20:12:31 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:31 mbt kioslave5[3355]: "Casting SessionData into subclass
failed."
Jul 19 20:12:31 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Casting SessionData into subclass failed."
Jul 19 20:12:32 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:32 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:32 mbt signond[12050]: signonsessioncore.cpp 397 replyError
Deprecated error code: 2
Jul 19 20:12:32 mbt signonpluginprocess[13250]: Operation requested while
plugin busy! - code 14
Jul 19 20:12:32 mbt kioslave5[3355]: "Failed to I/O session data to/from the
signon daemon."
Jul 19 20:12:32 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Failed to I/O session data to/from the signon daemon."
Jul 19 20:12:32 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:32 mbt kioslave5[3355]: "Casting SessionData into subclass
failed."
Jul 19 20:12:32 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Casting SessionData into subclass failed."
Jul 19 20:12:33 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:33 mbt signond[12050]: signonsessioncore.cpp 397 replyError
Deprecated error code: 2
Jul 19 20:12:33 mbt signonpluginprocess[13257]: Operation requested while
plugin busy! - code 14
Jul 19 20:12:33 mbt kioslave5[3355]: "Failed to I/O session data to/from the
signon daemon."
Jul 19 20:12:33 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Failed to I/O session data to/from the signon daemon."
Jul 19 20:12:33 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:33 mbt kioslave5[3355]: "Casting SessionData into subclass
failed."
Jul 19 20:12:33 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob
failed: "Casting SessionData into subclass failed."
Jul 19 20:12:33 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token
has expired or is invalid.
Jul 19 20:12:33 mbt signond[12050]: signonsessioncore.cpp 397 replyError
Deprecated error code: 2
Jul 19 20:12:33 mbt signonpluginprocess[13258]: 

[kde] [Bug 472394] NX Software Center crash

[Tobias Fella]

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

Tobias Fella  changed:

   What|Removed |Added

 CC||fe...@posteo.de
 Resolution|--- |MOVED
 Status|REPORTED|RESOLVED

--- Comment #1 from Tobias Fella  ---
This is not KDE softare. Bug reports should go to
https://github.com/Nitrux/nx-software-center, apparently.

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

[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)

[flan_suse]

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

--- Comment #27 from flan_suse  ---
(In reply to Forest from comment #25)
> Created attachment 160376 [details]
> draft: Kickoff from Plasma 5.27.5 with configurable sidebar position
> 
> I feel strongly that this should be configurable, so I decided to take on
> the work of making it so.
> 
> In case anyone wants to test it, here's a patched version of the Kickoff
> plasmoid from Plasma 5.27.5, patched with a new "sidebar position" option.

Just tested it, and it works as you described!

CAVEAT: In my opinion, the Legacy Launcher is still preferable, since it
already has a sane layout and is much snappier to use. (For reasons already
discussed by myself and a few others in this thread.)

Even when I move the "Favorites" to the left side, the "Application Categories"
(now on the right side) still suffers from the "Triangle Filter". So let's say
I want to go to my "Internet" applications. If I move my mouse too fast or at
the wrong angle, I'll accidentally end up going to "Office" or "Multimedia"
applications. :/ (I'm telling you, this new launcher slows down my workflow and
creates more problems than solutions. I hate being "conscious" about using a
menu launcher.)

This is not an issue with the Legacy Launcher, since it's layout is simpler and
easier to navigate. There's no need for any fancy "Triangle Filter" or
"predictions", since there's no risk of collisions or overlaps. (With the new
launcher, it's such a pain to quickly open up a file from the "History"; while
it's very easy and effortless to do so with the Legacy Launcher.)

Being able to choose which side your Favorites are displayed is definitely an
improvement for this new launcher. My appreciation to you!

Ironically, it feels like we're just re-inventing the Legacy Launcher. :P (I'm
still going to use the Legacy Launcher. I need to get work done, and I can't
feel like my desktop is creating friction or resistance. I don't want to have
to "think about" every time I use the launcher.)

Cluttering more things into "sub-panes" makes this new launcher feel crammed,
and more prone to collisions or accidents. The Legacy Launcher has large,
distinct "tabs" to effortlessly switch between modes: Favorites, Applications,
Places, History, Settings, Leave, etc. (You can even enable/disable the ones
you want.) No fancy mouse movements needed. Nothing's "crammed" together. The
new launcher crams "History" and "Places" together, but you need to navigate a
"sub-pane" to switch between them, and only after visiting the "Places" section
on the bottom. The same for "Favorites" and "Applications".

There's just too much going on in a crammed space with this new launcher.

It must also bear repeating: It's super annoying to have to consciously move my
mouse cursor vertically AS STRAIGHT AS POSSIBLE so that it registers
immediately what I hover over. If there's an "angle" or "skew" to my movement,
it doesn't register the item. (Luckily, this doesn't happen with the
"Favorites". It only affects the sub-panes that use a "Triangle Filter".)

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

[valgrind] [Bug 472402] memcheck "make tests" build fails: filter_sized_delete missing

[John Reiser]

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

--- Comment #2 from John Reiser  ---
Yes, this is part of a persistent local git clone, and I did run "./autogen.sh"
when I did the original clone.  I have run several successful "git pull; make
-j4" since then, over a span of several months.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[drkonqi] [Bug 472404] KDE Crash Handler never finishes "Submitting bug report..."

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|critical|crash

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

[valgrind] [Bug 472405] New: RFE: give Note about instructions on current hardware that are not supported by VEX

[John Reiser]

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

Bug ID: 472405
   Summary: RFE: give Note about instructions on current hardware
that are not supported by VEX
Classification: Developer tools
   Product: valgrind
   Version: unspecified
  Platform: PCLinuxOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: jrei...@bitwagon.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Request For Enhancement (RFE): At run-time initialization, then memcheck should
give a Note about cpu instructions on the current executing hardware, that VEX
does not support.  Such as: "Note: this version of valgrind does not support
these instructions of this CPU: aes bmi1 bmi2".  Such a Note would enhance
usability by giving early warning of Unrecognized Instruction.  Getting a
friendly warning at the beginning, instead of "vex amd64->IR: unhandled
instruction bytes: 0x..." and several lines of spew, is much more pleasant.

STEPS TO REPRODUCE
1. 
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.

[kate] [Bug 469406] Kate 23.04.0 crashing at start on macOS Ventura 13.3.1

[Waqar Ahmed]

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

Waqar Ahmed  changed:

   What|Removed |Added

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

--- Comment #11 from Waqar Ahmed  ---
Thanks for confirming. I guess Qt or whichever part of the stack that was
broken fixed itself.

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