[plasmashell] [Bug 487905] Launching Elisa pinned icon fails with notification error

2024-06-05 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=487905

--- Comment #6 from Harald Sitter  ---
(In reply to Marc from comment #5)
> or the application-launcher works just fine. 

Now that is interesting.

Looks like the app launcher does not use dbus invocation to start the
application. At face value that seems like a bug

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

[dolphin] [Bug 488055] New: Tags and ratings are VERY easy to accidentally delete.

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488055

Bug ID: 488055
   Summary: Tags and ratings are VERY easy to accidentally delete.
Classification: Applications
   Product: dolphin
   Version: 24.05.0
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: m1vri...@duck.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Currently it is incredibly easy to accidentally delete or lose tags. As I
understand it (I am not a developer) they are stored in extended attributes,
meaning any time a file is copied, moved or written over without maintaining
extended attributes, tags and ratings are lost.

• Using the cp command without “-a” will lose tags and ratings

• Using certain backup software like Timeshift will not backup tags and
ratings (use BorgBackup or a GUI for that like Vorta to make sure tags and
ratings are backed up)

• Saving over a file in an application that is not aware of tags will
delete the tags.

• Tags and ratings may not be copied from some mounted filesystems even
when using the same copy or move tools in Dolphin that would usually keep them

Some of the above may have proper solutions, and when they don’t they should be
clearly signposted for new users. Popups at specific times like when tagging
MIME types linked to apps that are not known to keep extended attributes when
saving would advise users to tag/rate the containing folder instead of the file
itself, or be aware the tag or rating may be saved over. There could be a first
time popup when adding tags or ratings to advise the user that the extended
attributes must me maintained to not lose the tag, and give examples of when
that may be.

I also wonder if it is possible for baloo to catch certain instances of
tags/ratings being accidentally removed and to have a popup that allows the
user to easily re-add them, with an explanation of how they got removed.

OBSERVED RESULT
Tags are unreliable and are erased unexpectedly.

EXPECTED RESULT
Have reliable tags that can be trusted enough to be used.

SOFTWARE/OS VERSIONS
NixOS 24.11 (unstable channel)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0 
Qt Version: 6.7.1

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

[kwin] [Bug 487057] After running an SDL application kwin_wayland uses 100% CPU even after the app is closed

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=487057

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from David Edmundson  ---
I cannot reproduce the results, and there isn't any other information in this
ticket that's actionable.

If you can reliably repeat the results can you include the output of:

qdbus org.kde.KWin /Effects org.kde.kwin.Effects.activeEffects

whilst CPU is high.

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

[dolphin] [Bug 488056] New: Renaming tags from tag fragments does not work as expected

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488056

Bug ID: 488056
   Summary: Renaming tags from tag fragments does not work as
expected
Classification: Applications
   Product: dolphin
   Version: 24.05.0
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: m1vri...@duck.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
When viewing tags from tag fragments (tags:/), it looks like you could rename a
tag and have that tag be changed on every file tagged that way. Dolphin allows
you to enter rename mode, but renaming a tag just results in an error, as well
as an erroneous removal of that tag from the list of tags.

STEPS TO REPRODUCE
1. Navigate to tags:/ or All Tags
2. Rename a tag

OBSERVED RESULT
Error popup window appears, "The file or folder tags:/[tag to be renamed] does
not exist." and the tag is removed from all tags, despite that tag still
existing.

EXPECTED RESULT
Everywhere that tag appears it is renamed, OR rename functionality is disabled
for tag fragments.

SOFTWARE/OS VERSIONS
NixOS 24.11 (unstable channel)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0 
Qt Version: 6.7.1

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

[kdenlive] [Bug 488053] Title - Delete animation

2024-06-05 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=488053

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

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

--- Comment #3 from Jean-Baptiste Mardelle  ---
I just fixed it in MLT:
https://github.com/mltframework/mlt/commit/fda7c026e959cfe9e549ad229827499cf8912bc7

As a workaround, you can right click on the clip in the project bin and select
"Reload Clip", this will correctly reset the animation. Save and reopen the
project will also fix it.

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

[dolphin] [Bug 488057] New: Filter by tags (Add Tags in search panel) could be easier to navigate. Requires scroll, other ways to search or shorten list of tags.

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488057

Bug ID: 488057
   Summary: Filter by tags (Add Tags in search panel) could be
easier to navigate. Requires scroll, other ways to
search or shorten list of tags.
Classification: Applications
   Product: dolphin
   Version: 24.05.0
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: search
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: m1vri...@duck.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
There is a filter by tags option in the search panel but it is very limited. It
currently doesn’t work at all (https://bugs.kde.org/show_bug.cgi?id=488047),
but when it did it consisted of a drop down menu of every tag in your entire
indexed system, which you can tick to only show items with those tags. This
list can be very long if you have a lot of tags and has no search function
within it; in fact it can be so long it can go off the bottom of the screen,
and there is no scroll function to get to the bottom of the list. A search
function and a scroll function for that Add Tags dropdown in the search panel
would go a long way to allowing users to sort through lots of tags. An even
more useful way to make that list easier to navigate would be to hide tags if
they would yield no results; that is, only show tags in the folder being
searched, that appear with the tags you have already selected.

STEPS TO REPRODUCE
1. Currently not reproducible as the menu is broken.

OBSERVED RESULT
(previous versions) Can view all tags and filter by them

EXPECTED RESULT
Can view all tags and filter by them, the list only showing tags that will
yield results, and to search tags from a potentially very long list.

SOFTWARE/OS VERSIONS
NixOS 24.11 (unstable channel)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0 
Qt Version: 6.7.1

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

[frameworks-baloo] [Bug 487916] Regressions in baloo in kf6 cause it to hog the machine

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=487916

--- Comment #6 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #5)
> ... Beyond that, I'm running out of ideas ...
On the off-chance that you are indexing hidden files and folders, you could
exclude the .cache and .local/share/Trash directories. They can be large and
busy

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

[frameworks-baloo] [Bug 487628] Baloo file indexer crashes on addition of new file

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=487628

--- Comment #7 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #5)
> ... I'll have a go at installing paperwork and exploring ...
I've done that although I'm not sure how clean an installation I managed. I
failed at the pacstrap step on a fresh install.

All the same, pulling an old installation off a backup and bringing it
up-to-date with Plasma 6, installing paperwork, sane, avahi and tesseract,
works (for me...)

I'd say, not with a large collection of test documents and with a fair number
of crashes caught and reported by paperwork but Baloo indexing seems OK.

Not sure what to suggest.

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

[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore

2024-06-05 Thread ezh
https://bugs.kde.org/show_bug.cgi?id=487566

--- Comment #26 from ezh  ---
I requested this feature, this a very useful feature. Sorry I could not test it
out. There is no way to beta test the changes... :(

I have an old notebook with Neon Unstable, but I cannot use it as a daily
driver, since very often after updates it just do not
work correctly and you have to wait for fixes for weeks...

KDE should really think how to change it. For example, allow to install a
program from unstable KDE Wear channel to a stable distribution.

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

[plasma-systemmonitor] [Bug 488044] Loading overlay doesn't cover full page when entering Edit Page mode

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=488044

David Redondo  changed:

   What|Removed |Added

 CC||k...@david-redondo.de
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[valgrind] [Bug 487993] Alignment error when using Eigen with Valgrind and -m32

2024-06-05 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=487993

--- Comment #6 from Paul Floyd  ---
I think that I see the cause.

https://elixir.bootlin.com/glibc/glibc-2.37/source/sysdeps/i386/malloc-alignment.h#L22

GNU libc has a special case for x86 bumping up the alignment to 16 bytes.

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

[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25

2024-06-05 Thread Denis
https://bugs.kde.org/show_bug.cgi?id=487370

--- Comment #45 from Denis  ---
Je vais avec grand plaisir me taire éternellement ! 🙂

J'ai pas besoin de logiciel remplis de bogues, des développeurs 
incompétent.  Attendre, attendre et toujours attendre dans l’hypothèse 
d'une éventuelle correction  😂😂 Aucune écoute.

Vos soucis de framework, de qt6 etc c'est pas mon problème. je m'en 
contre fiche totalement. 😕 Pourquoi faire simple, lorsqu'on peut faire 
compliquer. Pourquoi changer quelque qui fonctionne pour quelque qui ne 
fonctionne pas, c'est plus rigolos. Il faut changer pour quelque chose 
qui fonctionne mieux et non l'inverse.

,C'est chose faite, je vous laisse dans votre mascarade😛. Aillant 
effectuer plusieurs test sur différents logiciels et j'ai fais mon 
choix. Pour moi, le prix n'est absolument pas un problème et toutes 
manières cela n'ira jamais en améliorant ici, je préfère payer pour 
avoir un logiciel qui bug pas ou peu et d'un meilleur service de mise à 
jour (qui corrige vraiment ...). 😬. Je vous rassure, vous m'entendrez 
plus😂. Bon débarras. Je sais pas pourquoi et comment pour avoir choisit 
d'un telle logiciel, je m'en mords les doigts! 😂

Vous avez réussi a répondre en français ... quelle événement. C'est bien 
la première fois. Comme quoi en disant la vérité sa blesse.🙂

Maintenant, prenez la chose comme vous vous voulez, je m'en fou, je 
quitte le navire avec une extrême jouissance.🤐

J'ai hâte de la réponse ... s'il y a ?

😛😛😛   😂😂😂

L.e 05/06/2024 à 08:27, bugzilla_nore...@kde.org a écrit :
> https://bugs.kde.org/show_bug.cgi?id=487370
>
> --- Comment #43 from caulier.gil...@gmail.com ---
> Hi Denis,
>
> As your message is in French i continue in this language to be clear.
>
> Ce n'est pas un changement dans notre code mais un changement dans le 
> framework
> Qt. Sous Windows nous sommes passé de la 6.6.1 à la 6.7.0 pour intégrer un
> grande quantité de correction de bogues. Le bogue qui nous concerne est dans 
> Qt
> et uniquement sous Windows avec Qt6. Donc la complexité et de trouver le bon
> palliatif dans le code de digiKam tout en tenant compte des différentes
> versions de Qt et des autres architectures. C'est que qu'essaye de faire Maik
> actuellement. Ca prend du temps, du repackaging, des tests. Il faut être
> patient et tolérant, ou alors payer un logiciel propriétaire et se taire
>
> Cordialement
>
> Gilles Caulier
>

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

[plasmashell] [Bug 488042] Desktop freezes when bottom panel is hidden (Breeze theme)

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=488042

David Redondo  changed:

   What|Removed |Added

 CC||k...@david-redondo.de,
   ||xaver.h...@gmail.com
 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from David Redondo  ---
This is an issue of the nvidia driver with explicit sync.

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

[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25

2024-06-05 Thread Denis
https://bugs.kde.org/show_bug.cgi?id=487370

--- Comment #46 from Denis  ---
j'ai installer la toute dernière version 8.4 en date du 4 juin

Le 05/06/2024 à 08:41, Maik Qualmann a écrit :
> I would also like to point out that the latest digiKam-8.4.0 version does not
> crash when entering a name. Please test it from here:

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

[plasma-systemmonitor] [Bug 488030] CPU applet : bars not showing when the applet is in the panel since recent update

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=488030

David Redondo  changed:

   What|Removed |Added

Product|kdeplasma-addons|plasma-systemmonitor
 CC||ahiems...@heimr.nl,
   ||k...@david-redondo.de,
   ||plasma-b...@kde.org
   Assignee|plasma-b...@kde.org |ksysguard-b...@kde.org
  Component|General |general

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

[kwin] [Bug 488040] nigthcolor fails after wine/proton programs are open

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=488040

David Redondo  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
 CC||k...@david-redondo.de
  Component|kcm_nightcolor  |night color
Product|systemsettings  |kwin

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

[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=488022

David Redondo  changed:

   What|Removed |Added

 CC||k...@david-redondo.de
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from David Redondo  ---
Is that app maybe autostarted?

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

[plasmashell] [Bug 488042] Desktop freezes when bottom panel is hidden (Breeze theme)

2024-06-05 Thread Juan
https://bugs.kde.org/show_bug.cgi?id=488042

--- Comment #2 from Juan  ---
(In reply to David Redondo from comment #1)
> This is an issue of the nvidia driver with explicit sync.

Thanks for the heads up.
Will this be fixed in the NVIDIA 560 driver or will this be fixed in the
release of Plasma 6.1?

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

[plasmashell] [Bug 488023] plasmashell sometimes crashed in SystemClipboard::checkClipData::ClipboardMode after copying and pasting files in nautilus

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=488023

David Redondo  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||k...@david-redondo.de
 Resolution|--- |BACKTRACE

--- Comment #1 from David Redondo  ---
Thank you for the bug report! Unfortunately I can't reproduce the crash myself
on current git master, and the backtrace is missing debug symbols. 
Could you please install debug symbols and attach a new symbolicated backtrace
generated by using coredumpctl gdb in a terminal window (in textt form)? See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
for details about how to do this.
Thanks again!

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

[frameworks-baloo] [Bug 487628] Baloo file indexer crashes on addition of new file

2024-06-05 Thread Peter Kreussel
https://bugs.kde.org/show_bug.cgi?id=487628

--- Comment #8 from Peter Kreussel  ---
(In reply to tagwerk19 from comment #7)
> (In reply to tagwerk19 from comment #5)
> > ... I'll have a go at installing paperwork and exploring ...
> I've done that although I'm not sure how clean an installation I managed. I
> failed at the pacstrap step on a fresh install.
> 
> All the same, pulling an old installation off a backup and bringing it
> up-to-date with Plasma 6, installing paperwork, sane, avahi and tesseract,
> works (for me...)
> 
> I'd say, not with a large collection of test documents and with a fair
> number of crashes caught and reported by paperwork but Baloo indexing seems
> OK.
> 
> Not sure what to suggest.
Thanks for all your troubles.

What we found out is that baloo, perhaps only with qt 6.7.1, crashes on *some*
png files. On my Arch Linux system...

I have to disable  indexing the paperwork directory. Would be nice to have the
OCR'd text, which lies there in plain text files, in my KDE filesearch results,
but that obviously does not work at the moment. 

I am not enough into C++/QT/KDE programming to go deeper into this.

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

[kdevelop] [Bug 488043] KDevelop crashed when loading a KDevGenericManager project

2024-06-05 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=488043

Igor Kushnir  changed:

   What|Removed |Added

 CC||igor...@gmail.com

--- Comment #2 from Igor Kushnir  ---
(In reply to Davide Beatrici from comment #0)
> The crash happened almost immediately. Upon restarting the program, I chose
> to delete the cache and then I opened the project again, which was loaded 
> just fine.
Did you update Clang just before the crash occurred? Perhaps the cache is
incompatible between [major] libclang versions.

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

[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25

2024-06-05 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=487370

Maik Qualmann  changed:

   What|Removed |Added

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

--- Comment #47 from Maik Qualmann  ---
Under Windows 11, the problem will probably only be fixed with the next Qt
version...
We will have to wait until Qt-6.7.1 is available, until then digiKam-8.3.0 is
the stable release.

Maik

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

[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25

2024-06-05 Thread Bjørn Tore Hoem
https://bugs.kde.org/show_bug.cgi?id=487370

--- Comment #48 from Bjørn Tore Hoem  ---
Hi Maik - I have tested the new build and can confirm that facenames are
shown with background again.

However, this build introduces a new problem. If you remove an
existing name tag with a name, it crashes.
See this video: https://photos.app.goo.gl/UZnrRDJtK97aN9oK7

Thank you for looking into this:-)

Bjørn Tore

man. 3. juni 2024 kl. 21:05 skrev Maik Qualmann :

> https://bugs.kde.org/show_bug.cgi?id=487370
>
> --- Comment #40 from Maik Qualmann  ---
> I just made a change so that at least the face names are shown with a
> background again, it should be in the next build for tomorrow.
>
> We can't really do much here, it's a bug in Qt-6.7.0. It will be fixed
> with the
> next version Qt-6.7.1, when it is available to us in VCPKG it will be back
> to
> normal.
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[neon] [Bug 487374] Missing icons

2024-06-05 Thread Stephan Diestelhorst
https://bugs.kde.org/show_bug.cgi?id=487374

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections

2024-06-05 Thread Íñigo
https://bugs.kde.org/show_bug.cgi?id=350521

Íñigo  changed:

   What|Removed |Added

 CC||inigohug...@hotmail.com

--- Comment #24 from Íñigo  ---
We are adding some patches to NetworkManager that I expect that will make this
to work from KDE Plasma without any change required. It will need at least
NetworkManager 1.46.2 and NetworkManager-openvpn 1.12.0 (tentative, but
probable versions).

NetworkManager MR:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1958

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

[neon] [Bug 487374] Missing icons

2024-06-05 Thread Stephan Diestelhorst
https://bugs.kde.org/show_bug.cgi?id=487374

--- Comment #35 from Stephan Diestelhorst  ---
Note that this error (or related) prevents applications like discover from
running it seems like:

$ killall plasma-discover
$ plasma-discover
kf.config.core: Created a KConfigGroup on an inaccessible config location
":/icons/breeze/index.theme" "Icon Theme"
kf.config.core: Created a KConfigGroup on an inaccessible config location
":/icons/breeze/index.theme" "Icon Theme"
libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin")
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true

(process:9672): GLib-GObject-WARNING **: 09:31:18.973: cannot register existing
type 'SoupMessage'

(process:9672): GLib-GObject-WARNING **: 09:31:18.973: cannot add private field
to invalid (non-instantiatable) type ''

(process:9672): GLib-CRITICAL **: 09:31:18.973: g_once_init_leave: assertion
'result != 0' failed

(process:9672): GLib-GObject-WARNING **: 09:31:18.973:
../../../gobject/gsignal.c:1760: parameter 1 of type '' for signal
"SoupSession::request-queued" is not a value type

=> and then no window opens up

This is with the theme set to dark, but colours set to light so that I get to
see the icons.

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

[systemsettings] [Bug 480661] OpenConnect GlobalProtect VPN connection with SAML no longer works since RC2

2024-06-05 Thread Murz
https://bugs.kde.org/show_bug.cgi?id=480661

Murz  changed:

   What|Removed |Added

 CC||mur...@gmail.com

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

[plasmashell] [Bug 487905] Launching Elisa pinned icon fails with notification error

2024-06-05 Thread Marc
https://bugs.kde.org/show_bug.cgi?id=487905

--- Comment #7 from Marc  ---
Yes, it shows up as 
>dbus-:1.2-org.kde.elisa@0.service
under applications in system monitor when launched from the task manager. And
launched from the app launcher it shows as 
>Elisa
same behavior with both '24.02.2-1' and '24.05.0-1'.
But I discovered: You can launch multiple instances of 'elisa-24.05.0-1' when
launched from the app launcher. You can't do this with the older version. 
I looked through the source code of both versions with meld (but I am no
programmer, I must admit, so yeah) and I found some new code for 'KDbusService'
in 'elisaapplication.cpp', seems to be one of the biggest changes between
versions, could this be part of the problem?

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

[plasmashell] [Bug 488058] New: Clipboard history popup often misplaced (Wayland multimonitor with fractional scaling)

2024-06-05 Thread Andrea Ippolito
https://bugs.kde.org/show_bug.cgi?id=488058

Bug ID: 488058
   Summary: Clipboard history popup often misplaced (Wayland
multimonitor with fractional scaling)
Classification: Plasma
   Product: plasmashell
   Version: 6.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Clipboard
  Assignee: plasma-b...@kde.org
  Reporter: andrea.i...@gmail.com
  Target Milestone: 1.0

Created attachment 170161
  --> https://bugs.kde.org/attachment.cgi?id=170161&action=edit
screen arrangement

I have set Meta+V to show clipboard items at MOUSE position, yet whenever I
press that combo, the clipboard popup originates from the center of the screen.

This is very annoying especially since I keep a long history, and with this
positioning it's impossible for me to go at the end of the list, where the
arrow > to show more items is located. This is effectively limiting my history
to the items that fit within the first page (and not even all of it because
it's truncated).

I'm on Wayland with screen config as per attachment.

This issue happens on both the internal and external displays

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

[kwin] [Bug 488059] New: Overview effect freezes for about 45 seconds when attempting to shutdown/suspend/restart from within the overview effect

2024-06-05 Thread Philip Soerensen
https://bugs.kde.org/show_bug.cgi?id=488059

Bug ID: 488059
   Summary: Overview effect freezes for about 45 seconds when
attempting to shutdown/suspend/restart from within the
overview effect
Classification: Plasma
   Product: kwin
   Version: 6.0.5
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: 9f0cfw...@mozmail.com
  Target Milestone: ---

SUMMARY
When I attempt to shutdown, reboot or suspend using the overview effect to
search feature I experience a freeze approximately 45 seconds long during which
the system is non-responsive. Then, after the freeze, the KDE desktop session
screen opens like normal and I can proceed to shutdown/suspend/restart.

Running restart/shutdown/suspend from the KRunner works as expected, so the
issue appears to be isolated to the overview effect.

STEPS TO REPRODUCE
1.  Open overview effect
2.  In the search field, type "restart"
3. Select "Desktop sessions - Restart"  from the results and hit enter

OBSERVED RESULT
Instead of immediately opening the desktop sessions screen and starting the
restart countdown, the system first undergoes a total freeze for about 45
seconds. 

EXPECTED RESULT
After running "Desktop sessions - Restart", I expect to immediately open the
desktop session window and start the restart countdown. 

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.2-arch1-Adashima-T2-1-t2 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-1038NG7 CPU @ 2.00GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: Apple Inc.
Product Name: MacBookPro16,2
System Version: 1.0

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

[knetwalk] [Bug 486016] CTD malloc(): unaligned tcache chunk detected

2024-06-05 Thread Lone_Wolf
https://bugs.kde.org/show_bug.cgi?id=486016

--- Comment #7 from Lone_Wolf  ---
Just had another crash, but crash reporter was disabled so no logs. (re-enabled
now)

Versions 
KDE Plasma Version:  6.0.5
KDE Frameworks Version:  6.2.0
Qt Version: 6.7.1
Knetwalk version 24.05.0

kernel 6.9.3

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

[kwin] [Bug 488059] Overview effect freezes for about 45 seconds when attempting to shutdown/suspend/restart from within the overview effect

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=488059

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
   Priority|NOR |HI

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

[kwin] [Bug 488059] Overview effect freezes for about 45 seconds when attempting to shutdown/suspend/restart from within the overview effect

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=488059

David Redondo  changed:

   What|Removed |Added

 CC||k...@david-redondo.de

--- Comment #1 from David Redondo  ---
calls were made blocking for some bug
https://invent.kde.org/plasma/plasma-workspace/-/commit/81d61861608012e4d7a19e6f85b8d136c298f31f

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

[kwin] [Bug 487996] kwin do not get realtime capabilities on musl

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=487996

David Edmundson  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Priority|NOR |LO
 Status|REPORTED|CONFIRMED

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

[kwin] [Bug 487990] 3840x2160 monitor bounding box is not a rectangle

2024-06-05 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=487990

Zamundaaa  changed:

   What|Removed |Added

 CC||xaver.h...@gmail.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #4 from Zamundaaa  ---
KWin doesn't handle mouse cursor confinement or desktop size, there's something
wrong with your Xorg configuration instead. You can ask for help with that from
your distro.

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

[kwin] [Bug 487922] Alt-tab sometimes switches to the 2nd last open window instead of last open one.

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=487922

David Redondo  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||k...@david-redondo.de
 Status|REPORTED|NEEDSINFO

--- Comment #1 from David Redondo  ---
When this happens does the tab switcher window show up?

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

[kwin] [Bug 487901] kwin_nightlight: Error in time calculation. Deactivating Night Light

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=487901

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||k...@davidedmundson.co.uk
 Ever confirmed|0   |1

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

[kwin] [Bug 431643] Aurorae decoration engine is inefficient

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=431643

David Edmundson  changed:

   What|Removed |Added

 CC||thegeekyga...@protonmail.co
   ||m

--- Comment #11 from David Edmundson  ---
*** Bug 487827 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 487827] Dragging windows to maximize/restore is choppy with aurorae window decorations

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=487827

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---


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

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

[kwin] [Bug 487861] kwin crashed when opening a full-screen game unexpectedly, showing a black screen with the cursor visible

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=487861

David Redondo  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||k...@david-redondo.de
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from David Redondo  ---
Were you recording your screen at that time? Otherwise maybe kwin did not crash
but plasmashell? According to the backtrace the crash happened in screencasting
code. Kwin logs from journalctl might also be useful

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

[kwin] [Bug 487860] Nested kwin_wayland 6.0.90.1's window didn't appear in VMs using the llvmpipe driver

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=487860

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||k...@davidedmundson.co.uk
 Ever confirmed|0   |1

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

[kwin] [Bug 488060] New: Focus stealing prevention window rules are not enforced for the native Wayland apps

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488060

Bug ID: 488060
   Summary: Focus stealing prevention window rules are not
enforced for the native Wayland apps
Classification: Plasma
   Product: kwin
   Version: 6.0.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: rules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: f...@fedy.cz
CC: isma...@gmail.com
  Target Milestone: ---

SUMMARY
When using the "Window rules" system the "Focus stealing prevention" setting is
not enforced for native Wayland windows even at the "Force->Extreme" level.
Seems to be working fine for the legacy X11 windows like XTerm.


STEPS TO REPRODUCE
1. Make sure you are running under a Wayland session
2. Make a window rule for a native Wayland application (like Alacritty)
3. In the rule set the "Focus stealing prevention" to "Force" & "Extreme"
4. Apply the rule
5. Follow the steps 2-4. this time for a legacy X11 application (like XTerm)

OBSERVED RESULT
When new Wayland window is created it get the focus (every time) no matter the
rules set.
X11 applications follow the window rules so (in the example above) new XTerm
windows don't steal the current focus.


EXPECTED RESULT
Being able to prevent focus stealing (or maybe more specifically: stealing
focus on window creation) even for native Wayland applications. Can supply many
use cases on request.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora release 40 (Forty)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
- Tested that other parts of the rule are being applied (so the rule itself is
active)
- Using the "Focus follows mouse" windows activation policy by default, but
tested with "Click to focus" as well and no difference.

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

[kwin] [Bug 487857] Nested kwin_wayland 6.0.5 crashed in QRegion::QRegion in VMs using the llvmpipe driver

2024-06-05 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=487857

Zamundaaa  changed:

   What|Removed |Added

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

--- Comment #1 from Zamundaaa  ---
There won't be any 6.0 releases anymore, but according to bug 487860 it's fixed
in 6.1

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

[kwin] [Bug 487842] resizing window locks its location preventing moving it.

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=487842

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||k...@davidedmundson.co.uk
 Status|REPORTED|NEEDSINFO

--- Comment #1 from David Edmundson  ---
Do you use any screen scaling?

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

[kwin] [Bug 487840] Certain games have very low framerate under Wayland, yet both the games and KWin report normal FPS

2024-06-05 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=487840

Zamundaaa  changed:

   What|Removed |Added

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

--- Comment #2 from Zamundaaa  ---
I fixed some issues that could cause dropped frames after the beta was tagged;
please re-test once 6.1 is out

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

[kwin] [Bug 487833] Graphical Glitches in plasma 6.1

2024-06-05 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=487833

David Redondo  changed:

   What|Removed |Added

 CC||k...@david-redondo.de
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from David Redondo  ---
Does it only happen with Konsole? Is your konsole slightly transparent?

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

[kwin] [Bug 481222] Support proper output mirroring

2024-06-05 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=481222

Zamundaaa  changed:

   What|Removed |Added

 CC||leon.ha...@protonmail.com

--- Comment #4 from Zamundaaa  ---
*** Bug 487796 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 487796] When in "unify outputs" mode for dual screen setup, Overview effect does not show applications on the secondary monitor

2024-06-05 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=487796

Zamundaaa  changed:

   What|Removed |Added

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

--- Comment #1 from Zamundaaa  ---
This will be fixed once bug 481222 is fixed

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

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

[kwin] [Bug 488060] Focus stealing prevention window rules are not enforced for the native Wayland apps

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488060

f...@fedy.cz changed:

   What|Removed |Added

 CC||f...@fedy.cz

--- Comment #1 from f...@fedy.cz ---
Additional note:
Focus stealing prevention seem to be working for Wayland windows when set
globally (set Window Management -> Window Behavior -> Focus -> Focus stealing
prevention to "Extreme"). There just currently doesn't seem to be a way to make
rules for individual applications/windows using the "Window Rules" -> [rule] ->
"Focus stealing prevention" & "Focus protection" features (either way, whatever
the default).

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

[kwin] [Bug 487780] Fullscreen game stutter when Plasma receives notifications.

2024-06-05 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=487780

Zamundaaa  changed:

   What|Removed |Added

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

--- Comment #1 from Zamundaaa  ---
Can you test the same scenario after putting
KWIN_DRM_NO_DIRECT_SCANOUT=1
into /etc/environment and rebooting? Do you still see stutter then?

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

[kwin] [Bug 487771] kwin_x11 crashed 3 times when logging back in with momentary blurred graphic artifacts

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=487771

David Edmundson  changed:

   What|Removed |Added

 CC||kwil...@sc.edu

--- Comment #5 from David Edmundson  ---
*** Bug 480326 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 480326] kwin crashes in KWin::EffectsHandlerImpl::prePaintWindow() when starting Odamex with the OpenGL renderer

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=480326

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||k...@davidedmundson.co.uk

--- Comment #5 from David Edmundson  ---


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

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

[kwin] [Bug 437925] Crash in BlurEffect::blurRegion

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=437925

--- Comment #15 from David Edmundson  ---
*** Bug 474839 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 474839] Kwin crashes in KWin::BlurEffect::blurRegion() when moving tabs out of Firefox window and back

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=474839

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||k...@davidedmundson.co.uk
 Status|REPORTED|RESOLVED

--- Comment #4 from David Edmundson  ---


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

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

[plasmashell] [Bug 487905] Launching Elisa pinned icon fails with notification error

2024-06-05 Thread medin
https://bugs.kde.org/show_bug.cgi?id=487905

--- Comment #8 from medin  ---
I confirm, downgrading to 24.02.2-1 seems to be working fine.

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

[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25

2024-06-05 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=487370

--- Comment #49 from Maik Qualmann  ---
Git commit f0d3008d4d6360e00c3fdd0385259fb61effa55b by Maik Qualmann.
Committed on 05/06/2024 at 10:19.
Pushed by mqualmann into branch 'master'.

Revert "try to apply style only to face name label"

M  +2-5core/utilities/facemanagement/widgets/assignnamewidget_p.cpp

https://invent.kde.org/graphics/digikam/-/commit/f0d3008d4d6360e00c3fdd0385259fb61effa55b

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

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=478556

krob...@o-0.pl changed:

   What|Removed |Added

 CC||krob...@o-0.pl

--- Comment #97 from krob...@o-0.pl ---
(In reply to Cristian Le from comment #95)
> Just confirming with Fedora 40 and 6.0.5, this was indeed resolved. Can't
> reproduce the issue anymore.

Unfortunately the issue is still alive on my side. I was so happy to see the
6.0.5 update appear, this issue is killing me, but unfortunately updating did
not help.

Details from system info:

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-35-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 62,5 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: Dell Inc.
Product Name: Latitude 5520

It's a KDE 6 fresh install (not a  5 -> 6 upgrade).

Am I allowed to change the status of this report or should I create another
one? I'm new here.

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

[digikam] [Bug 488061] New: the tool Image Mosaic Wall will crashes

2024-06-05 Thread Frank
https://bugs.kde.org/show_bug.cgi?id=488061

Bug ID: 488061
   Summary: the tool Image Mosaic Wall will crashes
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ImageEditor-Plugins
  Assignee: digikam-bugs-n...@kde.org
  Reporter: fwi...@web.de
  Target Milestone: ---

Hello,
I would like to create a mosaic image using the Image Mosaic Wall... tool
(Extras/Image Mosaic Wall..), which works well with the standard grid settings
of 100 x 100. However, if I change the grid settings, e.g. 150 x 150, and then
click on "Create Mosaic", the entire digikam program usually crashes without an
error message. Sometimes you also get an error message that the read operation
could not be carried out in the memory.
Perhaps you can fix the problem in a future version.
Many thanks and best regards
Frank

STEPS TO REPRODUCE
1.  open the Tool Image Mosaic Wall
2.  create a mosaic with the default settings
3.  change the default settings (for example grid settings 150 x150)
4. click the button "Create Mosaic" the program will crashes immediately

OBSERVED RESULT
- the program crashes immediately

EXPECTED RESULT
- creation of the mosaic

SOFTWARE/OS VERSIONS
Windows: 11 
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.

[digikam] [Bug 488061] the tool Image Mosaic Wall will crashes

2024-06-05 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=488061

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kwin] [Bug 488062] New: Extreme CPU Usage by Kwin_X11

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488062

Bug ID: 488062
   Summary: Extreme CPU Usage by Kwin_X11
Classification: Plasma
   Product: kwin
   Version: 6.0.5
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: performance
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugreport...@mailna.me
  Target Milestone: ---

SUMMARY
***
Kwin_X11 constantly uses ridiculous amount of CPU. In extreme cases 60%. Must
be dealt with top priority.
***

STEPS TO REPRODUCE
1. Open 50fps avc1 video via SMPlayer/mpv
2. Watch it in a) a window b) full screen
3. click Konsole (you removed ctrl+at+t, not my fault, you have to click, or
type...)
5. type "top" (don't use htop, it calculates wrong...).

OBSERVED RESULT
Unacceptable extreme use of CPU by Kwin_X11


EXPECTED RESULT:

1. Revert the regression to make kwin operate as smoothly as in the times of
KDE 5.x. This regression puts kwin and by extension, the whole KDE6 in an alpha
stage "class". This is just Intel only, not even a "brand new, fancy"
Nvidia/AMD/AMD APU. Just Intel.

Imagine this: kwin in current state and non-gpu-accelerated video (eg. AV1) and
you have "kswapd0" disaster with lockdown/total freeze, even with zswap with
z3fold (to which you should switch instead of using the wrong default)
allocator and early module load of LZ4 (not zstd, which is the wrong default
again, because of RAM and CPU usage,...).

2. Reinstate the settings of kwin in system setting (regression of settings,
now its impossible to set any parameters of the compositor, the settings were
completely removed in KDE6 - users can't chose Open GL version or set any other
parameters, user doesn't know if kwin is using OpenGL v2 or 3. There are zero
settings* , e.g. speed/smoothness trade-off settings were removed, but even if
the the "trade-off" settings were there, in KD5 in the "smoothest" settings
kwin was never eating CPU or like in this KDE6 case, kwin in KDE5 had never had
a "CPU leakage"/constant CPU drainage). This is wrong, really wrong. 



SOFTWARE/OS VERSIONS
pacman -Qs:
local/kwin 6.0.5-2 (plasma) [older versions from KDE6 too]
local/kwindowsystem 6.2.0-1 (kf6)
local/kwindowsystem5 5.116.0-1 (kf5)

KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.6.32-1-lts/6.8.x/6.9.x (6.9.x has nasty bugs...)
Graphics Platform: X11
Memory: 3.7 GiB of RAM
Graphics Processor: Mesa Intel HD


asterix notations:
*All was purposely removed to cater to the lowest "MS dumb user denominator"
(just like double click instead of single click and "folder layout" instead of
"desktop"; please don't put any distro users in the same category...!)
**KDE users use krunner and home folder (often on separate block device).

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

[plasmashell] [Bug 487533] Notifications are sometimes shrinked on Plasma 6.1 Beta

2024-06-05 Thread Akseli Lahtinen
https://bugs.kde.org/show_bug.cgi?id=487533

Akseli Lahtinen  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/-/commi
   ||t/aa77ae7d752d3b258c720
   ||030b83233e214df
 Resolution|--- |FIXED

--- Comment #4 from Akseli Lahtinen  ---
Git commit aa77ae7d752d3b258c720030b83233e214df by Akseli Lahtinen.
Committed on 05/06/2024 at 10:49.
Pushed by akselmo into branch 'master'.

notifications/NotificationItem.qml: use implicitWidth only when grouped

Outside of group this will cause the notification to shrink,
but if preferredWidth is  completely removed, inside the group it will
take too much space and make the buttons out of screen.

M  +1-1applets/notifications/package/contents/ui/NotificationItem.qml

https://invent.kde.org/plasma/plasma-workspace/-/commit/aa77ae7d752d3b258c720030b83233e214df

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

[Bluedevil] [Bug 488063] New: https://www.garthtyrescardiff.co.uk/car-servicing

2024-06-05 Thread Tyrescardiff12
https://bugs.kde.org/show_bug.cgi?id=488063

Bug ID: 488063
   Summary: https://www.garthtyrescardiff.co.uk/car-servicing
Classification: Plasma
   Product: Bluedevil
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: libbluedevil
  Assignee: plasma-b...@kde.org
  Reporter: cardiffgarthty...@gmail.com
  Target Milestone: ---

Car Servicing in Cardiff is a mandatory for all car owners the car require
service once a year in uk. Garth tyres offers you the best car service at
reasonable price. you can buy tyres from their garage. 
https://www.garthtyrescardiff.co.uk/car-servicing

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

[Bluedevil] [Bug 488063] https://www.garthtyrescardiff.co.uk/car-servicing

2024-06-05 Thread Tyrescardiff12
https://bugs.kde.org/show_bug.cgi?id=488063

Tyrescardiff12  changed:

   What|Removed |Added

URL||https://www.garthtyrescardi
   ||ff.co.uk/car-servicing

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

[Bluedevil] [Bug 488063] The Secrets of Car Servicing in Cardiff Amateurs Know

2024-06-05 Thread Tyrescardiff12
https://bugs.kde.org/show_bug.cgi?id=488063

Tyrescardiff12  changed:

   What|Removed |Added

Summary|https://www.garthtyrescardi |The Secrets of Car
   |ff.co.uk/car-servicing  |Servicing in Cardiff
   ||Amateurs Know

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

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

2024-06-05 Thread Cristian Le
https://bugs.kde.org/show_bug.cgi?id=478556

--- Comment #98 from Cristian Le  ---
krob...@o-0.pl if you are able to reproduce with one of the reproducers in this
thread, than I think it's worth checking it again. Otherwise it could be
something more specific like in the case of firefox.

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

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

2024-06-05 Thread Nicolas
https://bugs.kde.org/show_bug.cgi?id=478556

--- Comment #99 from Nicolas  ---
Note that on Neon, kwin is still on 6.0.4

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

[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore

2024-06-05 Thread SigHunter
https://bugs.kde.org/show_bug.cgi?id=487566

SigHunter  changed:

   What|Removed |Added

 CC||sighun...@gmx.de

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

[kwin] [Bug 488062] Extreme CPU Usage by Kwin_X11

2024-06-05 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=488062

Nicolas Fella  changed:

   What|Removed |Added

   Severity|critical|normal
 CC||nicolas.fe...@gmx.de

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

[plasmashell] [Bug 488064] New: Application Launcher icon panel spacing seems to have increased

2024-06-05 Thread Peter
https://bugs.kde.org/show_bug.cgi?id=488064

Bug ID: 488064
   Summary: Application Launcher icon panel spacing seems to have
increased
Classification: Plasma
   Product: plasmashell
   Version: 6.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: plasma-b...@kde.org
  Reporter: p.wibber...@btinternet.com
  Target Milestone: 1.0

Created attachment 170162
  --> https://bugs.kde.org/attachment.cgi?id=170162&action=edit
Screenshot of upper panel.

SUMMARY

Since the 6.0.5 update, the Application Menu icon seems to occupy much more of
the panel than previously.  So much so, that the flexible-sized panel spacer is
reduced to zero width.  (In the attached screenshot, there is supposed to be a
panel spacer between the MATLAB icon and the Advanced Radio Player, but instead
there is excess padding associated with the Application Menu icon.)  

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT

SOFTWARE/OS VERSIONS

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-35-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: Dell Inc.
Product Name: XPS 13 9305 

ADDITIONAL INFORMATION

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

[Spam] [Bug 488063] The Secrets of Car Servicing in Cardiff Amateurs Know

2024-06-05 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=488063

Nicolas Fella  changed:

   What|Removed |Added

URL|https://www.garthtyrescardi |
   |ff.co.uk/car-servicing  |
 CC||nicolas.fe...@gmx.de
  Component|libbluedevil|Spam
   Assignee|plasma-b...@kde.org |n...@kde.org
Product|Bluedevil   |Spam

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

[plasmashell] [Bug 487533] Notifications are sometimes shrinked on Plasma 6.1 Beta

2024-06-05 Thread Akseli Lahtinen
https://bugs.kde.org/show_bug.cgi?id=487533

Akseli Lahtinen  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi
   |t/aa77ae7d752d3b258c720 |t/7a700862f820e6aff958ed712
   |030b83233e214df |9b62fb2b771ac45

--- Comment #5 from Akseli Lahtinen  ---
Git commit 7a700862f820e6aff958ed7129b62fb2b771ac45 by Akseli Lahtinen.
Committed on 05/06/2024 at 10:57.
Pushed by akselmo into branch 'Plasma/6.1'.

notifications/NotificationItem.qml: use implicitWidth only when grouped

Outside of group this will cause the notification to shrink,
but if preferredWidth is  completely removed, inside the group it will
take too much space and make the buttons out of screen.


(cherry picked from commit aa77ae7d752d3b258c720030b83233e214df)

9ebb3009 notifications/NotificationItem.qml: use implicitWidth only when
grouped

Co-authored-by: Akseli Lahtinen 

M  +1-1applets/notifications/package/contents/ui/NotificationItem.qml

https://invent.kde.org/plasma/plasma-workspace/-/commit/7a700862f820e6aff958ed7129b62fb2b771ac45

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

[kwin] [Bug 488059] Overview effect freezes for about 45 seconds when attempting to shutdown/suspend/restart from within the overview effect

2024-06-05 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=488059

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[digikam] [Bug 488061] the tool Image Mosaic Wall will crashes

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488061

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

   What|Removed |Added

  Component|ImageEditor-Plugins |Plugin-Generic-MosaicWall
 CC||caulier.gil...@gmail.com

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

[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore

2024-06-05 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=487566

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

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

[plasmashell] [Bug 487958] Num-lock key not selectable as a shortcut key

2024-06-05 Thread Maximilian Böhm
https://bugs.kde.org/show_bug.cgi?id=487958

--- Comment #4 from Maximilian Böhm  ---
No, "xmodmap -pke | grep Num_Lock" doesn’t show me anything with German Neo.

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

[digikam] [Bug 114223] New tool to build photomosaic using ImageMosaicWall

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=114223

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

   What|Removed |Added

  Component|Plugin-Editor-WishForNewToo |Plugin-Generic-MosaicWall
   |ls  |

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

[digikam] [Bug 424605] Cannot use Image Mosaic Wall on Windows

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=424605

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

   What|Removed |Added

  Component|Bundle-Windows  |Plugin-Generic-MosaicWall

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

[dolphin] [Bug 477298] Dolphin hangs when navigating to a directory with any JSON files in it

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=477298

sayantan.chaudhuri+...@gmail.com changed:

   What|Removed |Added

 CC||sayantan.chaudhuri+kde@gmai
   ||l.com

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

[systemsettings] [Bug 488065] New: Feature Request: all to search for keyboard shortcuts with "keybind(s)"

2024-06-05 Thread Techognito
https://bugs.kde.org/show_bug.cgi?id=488065

Bug ID: 488065
   Summary: Feature Request: all to search for keyboard shortcuts
with "keybind(s)"
Classification: Applications
   Product: systemsettings
   Version: 6.0.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kde.wh...@simplelogin.com
  Target Milestone: ---

SUMMARY
I would like to be able to search for "keybinds" or "keybind" and be taken to
the Keyboard Shortcuts setting

Many games uses keybinds for the setting used to change the different input,
and while I understand that it is not the same as keyboard shortcuts, my brain
writes in keybinds every time before I remember that it's called shortcuts.

Also looking at the list of potential duplicates show to me, that I am not
alone in calling Keyboard shourtcuts for keybinds

OBSERVED RESULT
searching for "keybind" or "keybinds" provide no result

EXPECTED RESULT
keywords should point to Keyboard Shortcuts

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 5850U with Radeon Graphics
Memory: 27,2 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 21A0004WMX
System Version: ThinkPad P14s Gen 2a

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 438884] create a kcm for UEFI/BIOS-settings for Thinkpad and DELL

2024-06-05 Thread Techognito
https://bugs.kde.org/show_bug.cgi?id=438884

Techognito  changed:

   What|Removed |Added

 CC||kde.wh...@simplelogin.com

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

[digikam] [Bug 488061] The tool Image Mosaic Wall will crashes under Windows

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488061

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

   What|Removed |Added

Summary|the tool Image Mosaic Wall  |The tool Image Mosaic Wall
   |will crashes|will crashes under Windows

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

[NeoChat] [Bug 488066] New: Neochat crashed after switching channels

2024-06-05 Thread Akseli Lahtinen
https://bugs.kde.org/show_bug.cgi?id=488066

Bug ID: 488066
   Summary: Neochat crashed after switching channels
Classification: Applications
   Product: NeoChat
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: akse...@akselmo.dev
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: neochat (24.07.70)
 (Compiled from sources)
Qt Version: 6.7.1
Frameworks Version: 6.4.0
Operating System: Linux 6.8.11-300.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.1.80 [CoredumpBackend]

-- Information about the crash:
I don't exactly remember what happened, but I think was switching between
channels.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  0x7f24d8641a91 in QArrayDataPointer::constEnd
(this=) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/tools/qarraydatapointer.h:127
#6  QList::constEnd (this=) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/tools/qlist.h:619
#7  indexOf (o=..., key=...,
keyExists=keyExists@entry=0x7ffdde3cea1f) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/serialization/qjsonobject.cpp:262
#8  0x7f24d86425fb in QJsonObject::valueImpl
(this=0x5b21508, key=...) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/serialization/qjsonobject.cpp:314
#9  QJsonObject::value (this=0x5b21508, key=...) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/serialization/qjsonobject.cpp:301


Reported using DrKonqi

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

[NeoChat] [Bug 488066] Neochat crashed after switching channels

2024-06-05 Thread Akseli Lahtinen
https://bugs.kde.org/show_bug.cgi?id=488066

--- Comment #1 from Akseli Lahtinen  ---
Created attachment 170163
  --> https://bugs.kde.org/attachment.cgi?id=170163&action=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[NeoChat] [Bug 488066] Neochat crashed after switching channels

2024-06-05 Thread Akseli Lahtinen
https://bugs.kde.org/show_bug.cgi?id=488066

--- Comment #2 from Akseli Lahtinen  ---
Added this for searchability

Thread 1 (Thread 0x7f24d249dd40 (LWP 5697)):
[KCrash Handler]
#5  0x7f24d8641a91 in QArrayDataPointer::constEnd
(this=) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/tools/qarraydatapointer.h:127
#6  QList::constEnd (this=) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/tools/qlist.h:619
#7  indexOf (o=..., key=...,
keyExists=keyExists@entry=0x7ffdde3cea1f) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/serialization/qjsonobject.cpp:262
#8  0x7f24d86425fb in QJsonObject::valueImpl
(this=0x5b21508, key=...) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/serialization/qjsonobject.cpp:314
#9  QJsonObject::value (this=0x5b21508, key=...) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/serialization/qjsonobject.cpp:301
#10 0x7f24daf95db9 in QJsonObject::operator[] (this=,
key=...) at /usr/include/qt6/QtCore/qjsonobject.h:61
#11 Quotient::RoomEvent::id (this=) at
/home/akseli/Repositories/kde/src/libquotient/Quotient/events/roomevent.cpp:24
#12 0x007224b2 in operator() (__closure=0x68f2310,
serverEvent=) at
/home/akseli/Repositories/kde/src/neochat/src/models/messagecontentmodel.cpp:78
#13 QtPrivate::FunctorCall,
QtPrivate::List, void,
MessageContentModel::initializeModel():: >::call
(f=..., arg=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#14
QtPrivate::FunctorCallable,
Quotient::RoomEvent*>::call, void>
(f=..., arg=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#15
QtPrivate::QCallableObject,
QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x68f2300, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#16 0x7f24d85fa752 in QtPrivate::QSlotObjectBase::call (this=0x68f2300,
r=, a=0x7ffdde3cec00) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobjectdefs_impl.h:469
#17 doActivate (sender=0x39b42a0, signal_index=10, argv=0x7ffdde3cec00)
at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:4086
#18 0x7f24d85f0b47 in QMetaObject::activate (sender=,
m=m@entry=0x7f24db07ab80, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffdde3cec00) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:4146
#19 0x7f24daf3f959 in Quotient::Room::pendingEventAboutToMerge
(this=, _t1=, _t1@entry=0x6dba340, _t2=, _t2@entry=0) at
/home/akseli/Repositories/kde/build/libquotient/QuotientQt6_autogen/include/moc_room.cpp:2366
#20 0x7f24daf6029d in Quotient::Room::Private::addNewMessageEvents
(this=this@entry=0x39b4350, events=...) at
/home/akseli/Repositories/kde/src/libquotient/Quotient/room.cpp:3106
#21 0x7f24daf61d85 in Quotient::Room::Private::addNewMessageEvents
(this=0x39b4350, events=...) at /usr/include/c++/14/bits/stl_iterator.h:1067
#22 Quotient::Room::updateData (this=0x39b42a0, data=..., fromCache=false) at
/home/akseli/Repositories/kde/src/libquotient/Quotient/room.cpp:2078
#23 0x7f24d85ebdeb in QObject::event (this=0x39b42a0, e=0x5021590) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:1452
#24 0x7f24d9b8b168 in QApplicationPrivate::notify_helper (this=, receiver=0x39b42a0, e=0x5021590) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/widgets/kernel/qapplication.cpp:3287
#25 0x7f24d8595b18 in QCoreApplication::notifyInternal2
(receiver=0x39b42a0, event=0x5021590) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1134
#26 0x7f24d8595d7d in QCoreApplication::sendEvent (receiver=, event=) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1575
#27 0x7f24d85998c1 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x17a30a0) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1932
#28 0x7f24d8599b6d in QCoreApplication::sendPostedEvents
(receiver=, event_type=) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1789
#29 0x7f24d887d39f in postEventSourceDispatch (s=0x1915620) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:244
#30 0x7f24d5b0f6ac in g_main_dispatch (context=0x7f24bc000f00) at
../glib/gmain.c:3344
#31 g_main_context_dispatch_unlocked (context=0x7f24bc000f00) at
../glib/gmain.c:4152
#32 0x7f24d5b70708 in g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7f24bc000f00, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4217
#33 0x7f24d5b10b23 in g_main_context_iteration (context=0x7f24bc000f00,
may_block=1) at ../glib/gmain.c:4282
#34 0x7f24d887cb53 in QEventDispatcherGlib::processEvents (this=0x17894d0,
flags=...) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qeventdis

[digikam] [Bug 488061] The tool Image Mosaic Wall will crashes under Windows

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488061

--- Comment #1 from caulier.gil...@gmail.com ---
Reported as UPSTREAM to
https://github.com/scheckmedia/ImageMosaicWall/issues/24

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

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=478556

--- Comment #100 from krob...@o-0.pl ---
(In reply to Nicolas from comment #99)
> Note that on Neon, kwin is still on 6.0.4

Oh, I thought if `KDE Plasma Version` in the system info is 6.0.5, then all
Plasma stuff, including kwin should also be on 6.0.5, if that's not the case
then ok, sorry for any confusion.

Is there a place with a schedule, when it's expected to be released within KDE
Neon? Initially I thought KDE Neon gets stuff as soon as they are released, I
was looking at this schedule: https://community.kde.org/Schedules/Plasma_6, but
KDE Plasma Version got bumped to 6.0.5 like 3 days ago for me, now I learned
that kwin is is not a part of this anyway

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

[kwin] [Bug 487842] resizing window locks its location preventing moving it.

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=487842

--- Comment #2 from p...@pfortin.com ---
(In reply to David Edmundson from comment #1)
> Do you use any screen scaling?
No.

Trying to reproduce as I write this, so you'll see my observations get more
specific as you read on...

Not sure it it's related; but when resizing windows, other strange things
happen:
- just now: an emacs window top edge was at top of screen; grabbing left edge
to resize width, the right edge bounces around like it's trying to stay in
place -- dragging left edge acts like a window move and right edge is trying to
compensate.
- moved (via title bar) this window so no edges touched screen edge; then,
trying to resize with left edge, window was now locked in place
- with a firefox window on middle screen and it right edge at screen's right
edge, resizing with left edge; right edge bounces around trying to stay in
place.

Seems like resize may be getting confused with move, bouncing between the two
functions.

Under closer examination, the window's right edge doesn't move; the window is
repainted over and over at high speed during resizing, creating lots of visual
artifacts giving the appearance of the right edge bouncing around -- mostly
it's the scroll bar that's changing width as the resizing proceeds. The scroll
bar's visual effects when resizing horizontally are:
- stretch: width stays the same
- shrink: scroll bar flashes widths 4 to 5 time normal width 

Wondering if there may be other ways to unlock the window's location,
accidentally discovered that during resizing, a window can suddenly lock its
size and location while still moving the mouse. Once locked, just clicking its
bottom edge also unlocks it.

So far, it's more reproducible by:
- move window 
- drag left edge back and forth
If this doesn't reproduce; try another window...

Trying on different apps:
- emacs is the worst as its repainting is very slow 
- firefox repaint is much faster, so scroll bar artifacts are slight
- claws-mail repaint is so fast, no artifacts are visible and repainting is
extremely smooth

More observations: emacs being the worst; trying to reproduce with that app... 
if emacs is displaying a file with short lines the repaints are faster; while
long lines require emacs to spend time recalculating what lines to display
based on wrapping. This long line recalculation increases the appearance of
wider scroll bars.

claws-mail is so fast that its wrapping is smooth and does not lock the window.

Starting to look like a race condition combined with repaint speed; but I'm not
a developer.

HTH

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

[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login

2024-06-05 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=488022

--- Comment #2 from S. Umar  ---
No, it is not. There is nothing in .config/autostart. Is there another place
for autostart? I see it in .config/ksmserverrc as:

[LegacySession: saved at previous logout]
clientMachine1=localhost
clientMachine2=localhost
command1=gkrellm
command2=gkrellm
count=2
--
I also see multiple instances I (after logging in and out) in kwin_saved\ at\
previous\ logout_
resourceClass1=Gkrellm
resourceClass2=Gkrellm
resourceClass3=plasmashell
resourceClass4=Gkrellm
resourceClass5=gkrellm
resourceClass6=plasmashell
resourceName1=gkrellm
resourceName2=gkrellm
resourceName3=plasmashell
resourceName4=gkrellm
resourceName5=gkrellm
resourceName6=plasmashell

..


wmCommand1=gkrellm\s
wmCommand2=gkrellm\s
wmCommand3=
wmCommand4=gkrellm\s
wmCommand5=gkrellm\s
wmCommand6=

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

[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login

2024-06-05 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=488022

--- Comment #3 from S. Umar  ---
Also in, .local/share/plasmasessionrestore/plasmasessionrestorestaterc 

[0]
appId=gnome-gkrellm.desktop

[1]
appId=gnome-gkrellm.desktop

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

[KPipeWire] [Bug 482594] Screen sharing/recording fails with error message "Failed to connect PipeWire context"

2024-06-05 Thread RustyStriker
https://bugs.kde.org/show_bug.cgi?id=482594

RustyStriker  changed:

   What|Removed |Added

 CC||avivr...@tutanota.com

--- Comment #9 from RustyStriker  ---
Same issue, trying to dig a bit but cannot really find anything, when running
xdg-desktop-portal-kde in the terminal i get the following:

error creating screencast "Failed to connect PipeWire context"
error creating screencast "Failed to connect PipeWire context"
xdp-kde-screencast: QScreen(0x5d650f439aa0, name="DP-3")
Screencasting::Metadata
xdp-kde-wayland-integration: failed to start streaming
ScreencastingStream(0x5d650fd00f00, name = "DP-3") "Failed to connect PipeWire
context"
xdp-kde-screencast: Invalid screen! 2 "0x0"

Tried digging a bit in xdg-desktop-portal-kde, and it seems to happen when the
ScreencastingStream object is emitting the failed signal under
QtWayland::zkde_screencast_Stream_unstable_v1which gets me into the cmake
generated files or something

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

[kdenlive] [Bug 488067] New: Cannot add title screen to project under GNU/Linux

2024-06-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=488067

Bug ID: 488067
   Summary: Cannot add title screen to project under GNU/Linux
Classification: Applications
   Product: kdenlive
   Version: 24.05.0
  Platform: Slackware
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: sombrag...@sombragris.org
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Cannot add a title screen

STEPS TO REPRODUCE
1.  Open Kdenlive, start a new project
2.  Open Project. See "Add Title Clip" grayed out
3.  Also selecting from templates gives invalid tests

OBSERVED RESULT
There is a message saying "Cannot open ".

This works with 24.05 under Windows 11 but under Slackware Linux does not.

EXPECTED RESULT
Kdenlive should be able to create and write titles, and put them in projects
and render them as part of the video file.

SOFTWARE/OS VERSIONS
Operating System: Slackware current 64 bit
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.3 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570


ADDITIONAL INFORMATION
I have no problems at all with file permissions, and previous Kdenlive (under
Plasma 5) versions worked well.

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

[kwin] [Bug 477738] [AMD, NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM

2024-06-05 Thread Ilya Bizyaev
https://bugs.kde.org/show_bug.cgi?id=477738

Ilya Bizyaev  changed:

   What|Removed |Added

Version|5.27.9  |6.0.5
 CC||bizy...@zoho.com

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

[kwin] [Bug 488062] Extreme CPU Usage by Kwin_X11

2024-06-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=488062

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
This is not a widespread issue, and not reproducible.

Lets focus on identifying what's wrong in your case rather than distracting
that with any other noise in your opening thread.

 - Can you confirm if this issue persists with any kwin scripts disabled and
the effects disabled.
 - Was the high CPU with both windowed and full screen modes?
 - Is this high from login or is there some other trigger?

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

[plasmashell] [Bug 488068] New: Custom bottom panel width leads to wrong position of panel on Plasma 6 X11

2024-06-05 Thread Maximilian Böhm
https://bugs.kde.org/show_bug.cgi?id=488068

Bug ID: 488068
   Summary: Custom bottom panel width leads to wrong position of
panel on Plasma 6 X11
Classification: Plasma
   Product: plasmashell
   Version: 6.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: m...@elbmurf.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 170164
  --> https://bugs.kde.org/attachment.cgi?id=170164&action=edit
Plasma 6 panel moved to first quarter of screen

Custom bottom panel width leads to wrong position of panel on Plasma 6 X11.

I have long used a custom panel width to separate the panel on the sides from
the screen corners, this worked flawlessly on Plasma 5. On Plasma 6 though, I
was greeted with my panel crammed at the first quarter of my monitor. See the
screenshot. In the screenshot, look at the bottom of the screen: There are
indicators of the custom panel width markers at center, that get ignored (but
my actual config is way wider than this).

This isn’t happening on Wayland sessions, logging into a Wayland session, my
panel is at the bottom with its custom width like configured.
I can flimsily rearrange the panel at the bottom on a X.Org session, correct
its width, but after a new login, it’s back at the first quarter of my screen
???

My monitor setup: Main monitor via DP with 4K, AV receiver connected via HDMI,
the AV receiver only supports FullHD. Some times, Kwin or the Plasma monitor
management get confused about the FullHD monitor and resize windows to its
size. But for this bug, I even have tested logging in with the AV receiver
turned off. So, it’s very strange.

But there is more: I have a custom length side panel with classical starters,
irregularly, it gets cut at the bottom. See the screenshot. This never happened
on Plasma 5.

STEPS TO REPRODUCE
1. Set a custom width to your bottom panel, non floating, monitor should
probably be 4K
2. On X.Org session login, your panel gets moved to the top left quarter of
your screen
3. Profit ??

Linux: Arch
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

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

[plasmashell] [Bug 488068] Custom bottom panel width leads to wrong position of panel on Plasma 6 X11

2024-06-05 Thread Maximilian Böhm
https://bugs.kde.org/show_bug.cgi?id=488068

--- Comment #1 from Maximilian Böhm  ---
Created attachment 170165
  --> https://bugs.kde.org/attachment.cgi?id=170165&action=edit
Cut-off side panel

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

[plasmashell] [Bug 488068] Custom bottom panel width leads to wrong position of panel on Plasma 6 X11

2024-06-05 Thread Maximilian Böhm
https://bugs.kde.org/show_bug.cgi?id=488068

Maximilian Böhm  changed:

   What|Removed |Added

 CC||m...@elbmurf.de

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

[kwin] [Bug 484037] Primary display loses its resolution configuration when resuming from sleep

2024-06-05 Thread Ed Tomlinson
https://bugs.kde.org/show_bug.cgi?id=484037

--- Comment #26 from Ed Tomlinson  ---
How does this solve the issue?  From the description of the commit it seems
that it is still going to set 640x480 but if I unplug and replug it will revert
to 2560x1440 which I selected manually previously.  If this is correct, I will
still need to run kscreen-doctor to set the correct reolution...

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

[kdevelop] [Bug 488069] New: Reproducible crash in libclang after ::Visitor::setTypeSize

2024-06-05 Thread Benjamin Huth
https://bugs.kde.org/show_bug.cgi?id=488069

Bug ID: 488069
   Summary: Reproducible crash in libclang after
::Visitor::setTypeSize
Classification: Applications
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: benjamin-h...@t-online.de
  Target Milestone: ---

SUMMARY

Today I observed an crash in KDevelop, and I was able to extract a single
source file that can reproduce the crash, see attached file (produced using g++
-E, so no includes required). 

The crash seems to happen in (anonymous namespace)::Visitor::setTypeSize in
src/plugins/clang/duchain/builder.cpp:950

KDevelop is built from sources against clang version 18.1.1 (Fedora
18.1.1-1.fc40).

In principle I'm willing to look into this, but currently I do not have time,
and maybe some experts already have an idea what this is.

Backtrace in gdb:

#0  0x7fffa0ee4104 in clang::ASTContext::getTypeInfoImpl(clang::Type
const*) const () at /lib64/libclang.so.18.1
#1  0x7fffa0ee5d5a in clang::ASTContext::getTypeInfoInChars(clang::Type
const*) const () at /lib64/libclang.so.18.1
#2  0x7fffa0ee5c50 in clang::ASTContext::getTypeInfoInChars(clang::Type
const*) const () at /lib64/libclang.so.18.1
#3  0x7fffa0ec4efc in clang_Type_getSizeOf () at /lib64/libclang.so.18.1
#4  0x7fffae29d9a6 in (anonymous namespace)::Visitor::setTypeSize
(type=..., kdevType=kdevType@entry=0x7fff83b924b0, this=)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:950
#5  0x7fffae2a069d in (anonymous
namespace)::Visitor::dispatchType<(CXTypeKind)177> (this=,
type=..., cursor=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:372
#6  (anonymous namespace)::Visitor::makeType (this=, type=...,
parent=...) at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:1466
#7  0x7fffae2aa455 in (anonymous
namespace)::Visitor::createType<(CXCursorKind)10> (this=0x7fffa0bff6a0,
cursor=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:707
#8  (anonymous namespace)::Visitor::createDeclaration<(CXCursorKind)10,
KDevelop::Declaration> (context=0x0, this=0x7fffa0bff6a0, cursor=..., id=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:457
#9  (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)10,
KDevelop::Declaration, false> (this=this@entry=0x7fffa0bff6a0, cursor=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:1296
#10 0x7fffae2b2d6f in (anonymous
namespace)::Visitor::dispatchCursor<(CXCursorKind)13, (Decision)1, (Decision)1>
(this=0x7fffa0bff6a0, cursor=..., parent=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:988


STEPS TO REPRODUCE
1. open empty session with empty project with attached file
2. wait a bit until background parser starts

OBSERVED RESULT
KDevelop crashes

EXPECTED RESULT
No crash

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.

[kdevelop] [Bug 488069] Reproducible crash in libclang after ::Visitor::setTypeSize

2024-06-05 Thread Benjamin Huth
https://bugs.kde.org/show_bug.cgi?id=488069

--- Comment #1 from Benjamin Huth  ---
Created attachment 170166
  --> https://bugs.kde.org/attachment.cgi?id=170166&action=edit
source file to reproduce the crash (wrapped in archive because of file size)

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

[plasmashell] [Bug 488023] plasmashell sometimes crashed in SystemClipboard::checkClipData after copying and pasting files in nautilus

2024-06-05 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=488023

Matt Fagnani  changed:

   What|Removed |Added

Summary|plasmashell sometimes   |plasmashell sometimes
   |crashed in  |crashed in
   |SystemClipboard::checkClipD |SystemClipboard::checkClipD
   |ata::ClipboardMode after|ata after copying and
   |copying and pasting files   |pasting files in nautilus
   |in nautilus |

--- Comment #2 from Matt Fagnani  ---
The crashing function is SystemClipboard::checkClipData(QClipboard::Mode mode)
based on
https://invent.kde.org/plasma/plasma-workspace/-/blob/master/klipper/systemclipboard.cpp#L124
I've tried to reproduce this problem a few more times, but it hasn't happened
again. I'll keep trying it. The problem might involve a race condition. Items
that I've copied in the host usually showed up at the top of the clipboard in
the VM and stayed there even after I copied something in the VM. Thanks.

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

  1   2   3   4   >