date:20250306

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

--- Comment #10 from matti-brandma...@web.de ---
Thank you for the advice! Ive been able to fix the issue by resetting my
.config through the files provided by /etc/skel, as after creating a new user
for testing, everything worked fine with this one. Still a mystery what caused
that after all, as the only thing I ever really did to customize was installing
the orchis theme for KDE. 
Thank you guys for your time!

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

[plasmashell] [Bug 501165] Constant crashes when running with wayland.

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

--- Comment #1 from j54jtjrztkt...@proton.me ---
Created attachment 179192
  --> https://bugs.kde.org/attachment.cgi?id=179192&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.

[plasmashell] [Bug 498593] Laptop goes into (broken) standby, if lid is closed during shut down

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

--- Comment #6 from fanzhuyi...@gmail.com ---
(In reply to Nate Graham from comment #3)
> I can reproduce this on a ThinkPad, but not on a different laptop, an HP
> Pavilion Plus 14.
> 
> That suggests that the behavior here is controlled by the device drivers,
> and not anything we can affect in Plasma code. I'd recommend reporting the
> issue upstream.

Humm looking at the plasma code [0], between the logout and shutdown request
[1], and the call to logind shutdown [2] [3], there is quite a lot of plasma
code going on, and I don't see anything particular that is blocking sleep
(maybe I am missing something obvious)

[0]
https://invent.kde.org/plasma/plasma-workspace/-/blob/master/startkde/plasma-shutdown/shutdown.cpp?ref_type=heads
[1]
https://invent.kde.org/plasma/plasma-workspace/-/blob/6ce316502af5110c18a6aa7dec6a03f4ca108808/startkde/plasma-shutdown/shutdown.cpp#L30
[2]
https://invent.kde.org/plasma/plasma-workspace/-/blob/6ce316502af5110c18a6aa7dec6a03f4ca108808/startkde/plasma-shutdown/shutdown.cpp#L171
[3]
https://invent.kde.org/plasma/plasma-workspace/-/blob/6ce316502af5110c18a6aa7dec6a03f4ca108808/libkworkspace/sessionmanagementbackend.cpp#L174

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

[plasmashell] [Bug 499383] plasma crashed in QtWaylandClient::QWaylandWindow::handleScreensChanged

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

Nate Graham  changed:

   What|Removed |Added

Version|6.3.0   |6.2.5

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

[plasmashell] [Bug 436318] Implement real session save/restore on Wayland

2025-03-06 Thread devsk

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

--- Comment #209 from devsk  ---
> All the apps I've used already remember their sizes on restarting, so I don't 
> bother with that.

konsole doesn't do that for me. It opens a single window of a dimension from
the profile.

My script opens as many konsole windows as you had open before, moves to the
right location in the right desktop and sizes them.

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

[Qt/KDE Flatpak Runtime] [Bug 500821] Flatpak application font mismatch since KDE 6.3.2

2025-03-06 Thread Jacopo Torrini

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

--- Comment #7 from Jacopo Torrini  ---
I ran the command and then launched Betterbird, but the problem persists. 
I've tried a bunch of application both from apt and flatpak and not all
applications have this problem:
Whatsapp Desktop (io.github.mimbrero.WhatsAppDesktop) have incorrect fonts.
Xournal++ doesn't.

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

[kdiff3] [Bug 499331] KDiff3 displays error message when saving a completed merge.

2025-03-06 Thread michael

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

michael  changed:

   What|Removed |Added

   Priority|NOR |HI

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

[plasmashell] [Bug 414502] (Un)plugging the AC adapter while screen is off always results in 100% brightness

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

TraceyC  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||kde...@tlcnet.info
 Resolution|--- |WAITINGFORINFO

--- Comment #3 from TraceyC  ---
Are either of you able to reproduce this on Plasma 6.3.2 or later?

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

[systemsettings] [Bug 500967] Allow custom keyboard commands/shortcuts to be disabled

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

--- Comment #4 from fanzhuyi...@gmail.com ---
(In reply to Nate Graham from comment #3)
> Being able to disable a custom shortcut's keyboard shortcut (or maybe even
> the whole thing) makes sense, but I would still encourage you to seek out a
> different solution for your use case here, as even if we implement this, it
> sounds like the result will still be uncomfortable and annoying.

Agreed. In most cases users just want to set or unset a shortcut, not
disable/enable custom shortcuts.

(In reply to insuna from comment #2)
> (In reply to Nate Graham from comment #1)
> > In this case, maybe Meta+F10 would be a better shortcut? Is
> > there a reason why that doesn't work for your use case?
> 
> The reason why Meta+F10 does not work for my case is twofold: 1) It's
> probably already bound to some default shortcut like "Switch to Workspace
> 10" and 2) I have a 65% keyboard that doesn't have a function-key row. Not
> only do I not have a Meta button on the right side of my keyboard, I also
> need to hit the Layer+ key to turn my Number-Row into the function row, and
> suddenly a 2-button shortcut is turned into a 3-button shortcut not unlike
> the 3-finger salute, just even more uncomfortable.

kmonad[0] may be a useful tool for your circumstances. It allows you to use
ordinary keys as modifiers when held (e.g., I configured my z,x,c, to also act
as ctrl, meta, and alt respectively, and similarly on the right).
If you are using a mechanical keyboard that supports QMK [1], that also
provides this functionality (and more) at a firmware level.

[0]: https://github.com/kmonad/kmonad
[1]: https://github.com/qmk/qmk_firmware/tree/master

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

[plasmashell] [Bug 501165] New: Constant crashes when running with wayland.

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

Bug ID: 501165
   Summary: Constant crashes when running with wayland.
Classification: Plasma
   Product: plasmashell
   Version: 6.3.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: j54jtjrztkt...@proton.me
  Target Milestone: 1.0

Application: plasmashell (6.3.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.11.0
Operating System: Linux 6.13.5-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.3.2 [CoredumpBackend]

-- Information about the crash:
It repedetly crashes once I log in, usually prompted by an alt+tab or opening a
systembar widget (like sound, network manager applets, etc.)
I run archlinux with wayland plasma with nvidia open dkms, I havent had
crashing issues before like this, only maybe in past month max, however I
havent been using wayland that much. If you require any further versioning
information for my system components or any info really, I'd be happy to
provide. Thank you for your time, freedom to us all, hackers!

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x7c4ba20a56d3 in __pthread_kill_internal (threadid=,
signo=6) at pthread_kill.c:89
#7  0x7c4ba204bba0 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7c4ba2033582 in __GI_abort () at abort.c:73
#9  0x7c4ba5271734 in wl_abort (fmt=fmt@entry=0x7c4ba52767f0 "Tried to add
event to destroyed queue\n") at ../wayland-1.23.1/src/wayland-util.c:476


Reported using DrKonqi

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

[krita] [Bug 500885] Exceeding cached frame size limit freezes canvas display after playing animation.

2025-03-06 Thread Emmet O'Neill

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

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WORKSFORME
 CC||emmetoneill@gmail.com

--- Comment #1 from Emmet O'Neill  ---
Hi Zane, 

When you say the canvas is freezing, do you mean that you are drawing on the
frame but not seeing the new lines?
Are you able to reproduce this bug consistently, or is it kind of random when
it happens?

As of now, I'm not able to reproduce this issue on my end (git master) even
with "cached frame size limit" set as low as possible.
I'm still able to play, pause, stop and then continue drawing without having
any issues with the canvas.

If there is any more info you can share (more detailed steps to reproduce, a
video recording, a test file, etc.) about what this bug looks like or how to
reproduce it, please let us know and I'll take another look at it.

Emmet

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

[krita] [Bug 500458] When pressing next frame button instead of just going to next frame, goes to previous frame then to next frame.

2025-03-06 Thread Emmet O'Neill

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

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||emmetoneill@gmail.com
 Resolution|--- |WORKSFORME

--- Comment #3 from Emmet O'Neill  ---
Hey Amadei, I'm not able to reproduce this issue. 

I've checked the "next frame", "previous frame", "next keyframe", "previous
keyframe", "next matching keyframe", and "previous matching keyframe" actions,
and all of them are working as I would expect. The next/previous frame and
keyframe buttons on the timeline are also working like expected.

Can you double-check your keyboard shortcut bindings and see if there isn't
something configured wrong?

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

[plasmashell] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot

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

TraceyC  changed:

   What|Removed |Added

 CC||kde...@tlcnet.info
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #12 from TraceyC  ---
Is anyone still having this problem on Plasma 6.3.2 or later?

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

[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[krunner] [Bug 500972] Search results within a category/runner don't seem to be ranked by frequency anymore

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

--- Comment #4 from Nate Graham  ---
Yeah, I can see in my ~/.local/share/krunnerstaterc file that under
[PlasmaRunnerManager][History], the sole item in there gets updated, but under
[PlasmaRunnerManager], LaunchCounts= does NOT get updated.

So the ordering of items determined by launch counts in the past are now
frozen.

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

[kwin] [Bug 500909] No screencast/window thumbnail functionality works

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

--- Comment #11 from Nate Graham  ---
Was it a global theme? Can you find the URL for it?

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

[plasmashell] [Bug 489556] When screen timer is allowed to run out and auto lock, brightness is turned down

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

TraceyC  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||kde...@tlcnet.info
 Status|REPORTED|NEEDSINFO

--- Comment #1 from TraceyC  ---
I'm sorry we weren't able to get to this report before now. Is this still
happening with Plasma 6.3.2?

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

[plasmashell] [Bug 499654] plasmashell crashes in QMimeData::hasImage() when dragging panel widgets

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

Nate Graham  changed:

   What|Removed |Added

   Priority|HI  |NOR
Summary|plasmashell crashes when|plasmashell crashes in
   |dragging panel widgets  |QMimeData::hasImage() when
   ||dragging panel widgets

--- Comment #4 from Nate Graham  ---
It's only #26 on
https://crash-reports.kde.org/organizations/kde/issues/?limit=5&project=9&query=error.unhandled%3Atrue%20is%3Aunresolved&sort=freq&statsPeriod=30d;
lowering severity.

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

[plasmashell] [Bug 499654] plasmashell crashes in QMimeData::hasImage() when dragging panel widgets

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

Nate Graham  changed:

   What|Removed |Added

   Sentry Crash||https://crash-reports.kde.o
 Report||rg/organizations/kde/issues
   ||/45244/

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

[plasmashell] [Bug 494497] Screen brightness is being changed even though "change screen brightness" is disabled.

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

TraceyC  changed:

   What|Removed |Added

 CC||kde...@tlcnet.info
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=495747

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

[kwin] [Bug 401271] Panel on second screen restricts movement on first

2025-03-06 Thread Vlad Zahorodnii

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

Vlad Zahorodnii  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/kwin/-/commit/76516a10c0 |ma/kwin/-/commit/cb0e06d290
   |230e0bc5d3fc65e3998425075a6 |0add3387e235a62f94cbfb914d0
   |cda |deb

--- Comment #15 from Vlad Zahorodnii  ---
Git commit cb0e06d2900add3387e235a62f94cbfb914d0deb by Vlad Zahorodnii, on
behalf of Yifan Zhu.
Committed on 06/03/2025 at 22:09.
Pushed by vladz into branch 'Plasma/6.3'.

window: reimplement restriction in moveResize

In restricted moveResize, try to guarantee at least a 100px contiguous
block of the titlebar is visible. Previously this was implemented by
shifting the geometry by 1px increments, trying to find a suitable
position. This is inefficient and error-prone.

Replace this with an efficient algorithm that finds the closest
candidate position. Consolidate the restriction code and add tests.
Related: bug 481610, bug 493797
(cherry picked from commit 76516a10c0230e0bc5d3fc65e3998425075a6cda)

M  +396  -1autotests/integration/move_resize_window_test.cpp
M  +3-3autotests/integration/x11_window_test.cpp
A  +---doc/moveresizerestriction/moveresizerestriction.pdf
A  +232  -0doc/moveresizerestriction/moveresizerestriction.tex
M  +266  -172  src/window.cpp
M  +1-1src/window.h

https://invent.kde.org/plasma/kwin/-/commit/cb0e06d2900add3387e235a62f94cbfb914d0deb

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

[Discover] [Bug 500661] Updates list sorted alphabetically shouldn't be case-sensitive - offline edition

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

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=499638

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

[killbots] [Bug 497856] grid and robots are mis-aligned on my tablet

2025-03-06 Thread Unknown

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

--- Comment #1 from Salvo "LtWorf" Tomaselli  ---
This happens on all wayland sessions.

Passing -platform xcb is a valid workaround. I'll patch the .desktop file on
Debian to always launch using X11 to keep the game playable.

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

[plasmashell] [Bug 501166] New: When placed in panel with multiple spacers, the Media Player widget is always slightly too small for the text to fit

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

Bug ID: 501166
   Summary: When placed in panel with multiple spacers, the Media
Player widget is *always* slightly too small for the
text to fit
Classification: Plasma
   Product: plasmashell
   Version: 6.3.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Media Player widget
  Assignee: plasma-b...@kde.org
  Reporter: darx...@outlook.com
CC: k...@privat.broulik.de
  Target Milestone: 1.0

Created attachment 179193
  --> https://bugs.kde.org/attachment.cgi?id=179193&action=edit
A screenshot of the widget displaying "Alpha" by C418, but the word Alpha is
cut off to "Alp..."

SUMMARY
When the Media Player widget is placed in a panel with 2 or more spacers, the
title on the widget is always slightly cut off, no matter how long the text is.

STEPS TO REPRODUCE
1. Create a panel
2. Add the Media Player widget to it
3. Add 2 or more spacers with flexible size to the panel
4. Play a video or song

OBSERVED RESULT
Even if there is enough space for the full title, the last few characters are
always cut off behind an ellipsis ("...")

EXPECTED RESULT
If there is enough space for the full video/song/etc title to fit, then it
should display the entire title

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION

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

[kcalc] [Bug 500784] kcalc allows to input multiple decimal points

2025-03-06 Thread Gabriel Barrantes

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

--- Comment #7 from Gabriel Barrantes  ---
(In reply to Imron from comment #6)
> Hello, yes I see how this works now. I think on invent KDE there is already
> a commit about the multiple decimal insertion. Is it still actual for me to
> work on this or the change is already approved?

Hasn't, talk to the guy is working on it, see if he wants some help.

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

[kcalc] [Bug 501000] Using the square root function in science mode leads to "Malformed expression"

2025-03-06 Thread Gabriel Barrantes

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

--- Comment #3 from Gabriel Barrantes  ---
(In reply to prep from comment #2)
> Previously, the root and other functions were calculated from the displayed
> content of the input field, why not return exactly this behavior. If there
> are no brackets, then it is obvious. Well, or add a check for switching?

because that would be incompatible with the input display that allows the input
to be edited. I need to do some changes so the blinking cursor is always
visible but since now you can edit the input that old behaviour is just not
compatible.

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

[digikam] [Bug 501163] reject the suggestion

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

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

   What|Removed |Added

   Severity|normal  |wishlist
  Component|Faces-Recognition   |Faces-Workflow
 CC||caulier.gil...@gmail.com

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

[Spectacle] [Bug 500042] Spectacle quits prematurely copying large screenshots when its "New Screenshot Saved" popup is disabled

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

--- Comment #7 from Bug Janitor Service  ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it will be automatically closed as
RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read
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.

[krusader] [Bug 495435] Krusader crashes if "Properties" dialog is invoked for a directory via context menu fresh after start

2025-03-06 Thread Serge Roussak

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

Serge Roussak  changed:

   What|Removed |Added

 CC||beaux_mo...@tut.by

--- Comment #15 from Serge Roussak  ---
This annoying issue is reproduced on my ArchLinux too. It's being fired in both
of the Krusader and the Dolphin. It doesn't lead to theirs crash, but to the
main window disappearing for a moment. It's reproduced for the first Properties
invocation only and for a (single) folder only. It doesn't matter if I choose
it via the context menu or using the shortcut. It isn't reproduced if I select
multiple folders or a single or multiple files, but even after successful
Properties invocation (e.g. for the multiple folders) the first attempt to open
the Properties window for a single folder lead to the behaviour described.
After this the Properties window opening works as expected in this
Krusader/Dolphin instance.

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

[okular] [Bug 501170] New: Editing pdf formt fields

2025-03-06 Thread Unknown

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

Bug ID: 501170
   Summary: Editing pdf formt fields
Classification: Applications
   Product: okular
   Version: 22.12.3
  Platform: KDE Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: k...@vonsengbusch.de
  Target Milestone: ---

Application: okular (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 5.14.21-150500.55.88-default x86_64
Windowing System: X11
Distribution: "openSUSE Leap 15.5"
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
The crash occurred, when editing a format text field

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault

[KCrash Handler]
#4  0x7f7ddbdc9cfc in GfxResources::doLookupFont(char const*) const () from
/usr/lib64/libpoppler.so.126
#5  0x7f7ddbdc9e0d in GfxResources::lookupFont(char const*) () from
/usr/lib64/libpoppler.so.126
#6  0x7f7ddbdaf308 in Form::ensureFontsForAllCharacters(GooString const*,
std::__cxx11::basic_string, std::allocator >
const&, GfxResources*) () from /usr/lib64/libpoppler.so.126
#7  0x7f7ddbdaf926 in ?? () from /usr/lib64/libpoppler.so.126
#8  0x7f7e150e2117 in Poppler::FormFieldText::setText(QString const&) ()
from /usr/lib64/libpoppler-qt5.so.1
#9  0x7f7e1a576994 in ?? () from /usr/lib64/libOkular5Core.so.10
#10 0x7f7e2121f396 in QUndoStack::push(QUndoCommand*) () from
/usr/lib64/libQt5Widgets.so.5
#11 0x7f7e1a5523bf in Okular::Document::editFormText(int,
Okular::FormFieldText*, QString const&, int, int, int) () from
/usr/lib64/libOkular5Core.so.10
#12 0x7f7e1a928ebd in ?? () from /usr/lib64/qt5/plugins/okularpart.so
#13 0x7f7e202a991b in ?? () from /usr/lib64/libQt5Core.so.5
#14 0x7f7e1a89930d in ?? () from /usr/lib64/qt5/plugins/okularpart.so
#15 0x7f7e1a921102 in ?? () from /usr/lib64/qt5/plugins/okularpart.so
#16 0x7f7e202a991b in ?? () from /usr/lib64/libQt5Core.so.5
#17 0x7f7e20fe07b5 in QLineEdit::textEdited(QString const&) () from
/usr/lib64/libQt5Widgets.so.5
#18 0x7f7e20fdddc4 in ?? () from /usr/lib64/libQt5Widgets.so.5
#19 0x7f7e20fe702d in ?? () from /usr/lib64/libQt5Widgets.so.5
#20 0x7f7e202a9695 in ?? () from /usr/lib64/libQt5Core.so.5
#21 0x7f7e20fe7ba5 in QWidgetLineControl::textEdited(QString const&) ()
from /usr/lib64/libQt5Widgets.so.5
#22 0x7f7e20feaf1b in QWidgetLineControl::finishChange(int, bool, bool) ()
from /usr/lib64/libQt5Widgets.so.5
#23 0x7f7e20fee0fc in QWidgetLineControl::processKeyEvent(QKeyEvent*) ()
from /usr/lib64/libQt5Widgets.so.5
#24 0x7f7e20fe085a in QLineEdit::keyPressEvent(QKeyEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#25 0x7f7e20ee0577 in QWidget::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#26 0x7f7e20fe678a in QLineEdit::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#27 0x7f7e1a927038 in ?? () from /usr/lib64/qt5/plugins/okularpart.so
#28 0x7f7e20e9f53c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#29 0x7f7e20ea72e3 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#30 0x7f7e2026bf23 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#31 0x7f7e20efd5e8 in ?? () from /usr/lib64/libQt5Widgets.so.5
#32 0x7f7e20e9f53c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#33 0x7f7e20ea62ff in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#34 0x7f7e2026bf23 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#35 0x7f7e2074677b in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() from /usr/lib64/libQt5Gui.so.5
#36 0x7f7e2074b075 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib64/libQt5Gui.so.5
#37 0x7f7e20721b8b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib64/libQt5Gui.so.5
#38 0x7f7e1c10f65a in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#39 0x7f7e1dac182b in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#40 0x7f7e1dac1bd0 in ?? () from /usr/lib64/libglib-2.0.so.0
#41 0x7f7e1dac1c5c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#42 0x7f7e202ce86c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#43 0x7f7e2026a78a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#44 0x7f7e20273fc7 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#45 0x55edeb735047 in ?? ()
#46 0x7f7e1fb7d24d in __libc_start_main () fr

[plasmashell] [Bug 501167] New: plasmashell crash after changing workspaces via the bar

2025-03-06 Thread Micah Shennum

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

Bug ID: 501167
   Summary: plasmashell crash after changing workspaces via the
bar
Classification: Plasma
   Product: plasmashell
   Version: 6.3.2
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: jimt...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.3.2)
 (Compiled from sources)
ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.11.0
Operating System: Linux 6.13.5-gentoo x86_64
Windowing System: Wayland
Distribution: "Gentoo Linux"
DrKonqi: 6.3.2 [CoredumpBackend]

-- Information about the crash:
I unlockd my computer, checked webbrowser, then tried to switch to another
workspace via clicking the area in the bar. The bar "froze" for a second or
two, showing the windows from the old workspace (I did see windows for the new
workspace visible "for real"), then the bar blinked out/reloaded and I got this
plasmashell crash dialog. I tried changing back and forth among desktops a few
times, but it didn't happend again. Incase it matters, I'm using wayland on
nvidia drivers.

The crash does not seem to be reproducible.

-- Backtrace (Reduced):
#4  0x7f87e9e733be in QSharedPointer::data (this=) at /usr/include/qt6/QtCore/qsharedpointer_impl.h:274
#5  QSharedPointer::operator-> (this=) at
/usr/include/qt6/QtCore/qsharedpointer_impl.h:280
#6  PipeWireSourceStream::renegotiateModifierFailed (this=0x0,
format=SPA_VIDEO_FORMAT_BGRx, modifier=216172782120099856) at
/var/tmp/portage/kde-plasma/kpipewire-6.3.2/work/kpipewire-6.3.2/src/pipewiresourcestream.cpp:263
#7  0x7f8840b04de3 in QObject::event (this=0x562a0958dcb0,
e=0x7f882c00d440) at
/usr/src/debug/dev-qt/qtbase-6.8.2-r2/qtbase-everywhere-src-6.8.2/src/corelib/kernel/qobject.cpp:1418
#8  0x7f8842cf4ba8 in QApplicationPrivate::notify_helper (this=, receiver=0x562a0958dcb0, e=0x7f882c00d440) at
/usr/src/debug/dev-qt/qtbase-6.8.2-r2/qtbase-everywhere-src-6.8.2/src/widgets/kernel/qapplication.cpp:3296


Reported using DrKonqi

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

[kdeconnect] [Bug 500825] KDE connect crashed multiple times on startup

2025-03-06 Thread Jakob Petsovits

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

--- Comment #7 from Jakob Petsovits  ---
Let's link to the commit in Invent:
https://invent.kde.org/network/kdeconnect-kde/-/commit/d04a3336bc2855880ac9a9591f3ec907c6f8dc36

There is a straightforward bug in this commit, in this change:

> - obj.insert(QLatin1String("id"), m_id);
> + obj.insert(QLatin1String("id"), QDateTime::currentMSecsSinceEpoch());

m_id was a QString though, so this line should likely adopt the
QString::number() conversion that the m_id initializer was using before:

> obj.insert(QLatin1String("id"), 
> QString::number(QDateTime::currentMSecsSinceEpoch()));

However, fixing the type for the "id" property does not seem to make it work.
Still crashing. I'm not sure what else is going wrong here.

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

[systemsettings] [Bug 500933] Turning on power management in Settings after modifying the default font causes the Settings app to freeze

2025-03-06 Thread 19484

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

--- Comment #2 from 19484 <1948486...@qq.com> ---
Created attachment 179195
  --> https://bugs.kde.org/attachment.cgi?id=179195&action=edit
Turning on power management in Settings after modifying the default font causes
the Settings app to freeze

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

[kwin] [Bug 498280] Compositor latency causes input lag

2025-03-06 Thread Rolf Schröder

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

--- Comment #7 from Rolf Schröder  ---
As a short update here: I currently have an alias `recover-amdgpu` (`sudo cat
/sys/kernel/debug/dri/1/amdgpu_gpu_recover'`)  which I only use when necessary.
Because: At work, I connect the machine (Thinkpad T14) to a docking station
(which has an external monitor connected to it) - here, I *never* experience
the issue. When working without the docking station (i.e. "mobile"), I *always*
have the problem. It manifests already during login (i.e. typing the password
lags).

The alias has work always except for a single time. Upon invocation, the screen
turns black, comes back again and KDE reports a little information about
"desktop effects" (not always). The one time it did not work, the screen turned
off/on several times until eventually the command prompt appeared again.
However, the lag did not go away. The only thing I did differently here was to
activate the Night Light. I rebooted and `recover-amdgpu`'ed and it worked
again (Night Light was then already enabled since I had activated in just
before).

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

[kwin] [Bug 500329] Logitech Marble FX Trackball Paste Button not configurable under Wayland

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

--- Comment #7 from Bug Janitor Service  ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it will be automatically closed as
RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read
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.

[plasmashell] [Bug 500443] Crash when playing with some elements of the plasma shell

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

--- Comment #9 from Bug Janitor Service  ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it will be automatically closed as
RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read
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.

[amarok] [Bug 489856] collection scanner fails/no files displayed

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

--- Comment #5 from Bug Janitor Service  ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it will be automatically closed as
RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read
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.

[plasmashell] [Bug 500878] Sleep with keyboard shortcut triggers sleep again on the next waking up

2025-03-06 Thread Sin Jeong-hun

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

--- Comment #8 from Sin Jeong-hun  ---
(In reply to Nate Graham from comment #7)
> Thanks, I thought it sounded familiar.
> 
> *** This bug has been marked as a duplicate of bug 493974 ***

It does not look like the same problem to me. The computer is a desktop PC with
two DP monitors. There is no lid. It does not happen if I put the PC to sleep
using the sleep button on the KickOff menu.

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

[kdeconnect] [Bug 500825] KDE connect crashed multiple times on startup

2025-03-06 Thread Jakob Petsovits

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

Jakob Petsovits  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #6 from Jakob Petsovits  ---
I had a look at some of the commits to track down the cause.

It looks like commit d04a3336bc2855880ac9a9591f3ec907c6f8dc36 in kdeconnect-kde
is the culprit. By reverting to the commit immediately before and restarting
kdeconnectd, the problem stops happening.

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

[digikam] [Bug 501163] Add the way to reject the suggestion of face in preview.

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

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

   What|Removed |Added

Summary|reject the suggestion   |Add the way to reject the
   ||suggestion of face in
   ||preview.

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

[kwin] [Bug 501094] Freeze when selecting "Prefer color accuracy"

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

--- Comment #8 from riso...@gmail.com ---
kscreen doctor with external monitor connected
(base) [Riso@x ~]$ kscreen-doctor -o
Output: 1 eDP-1
enabled
connected
priority 2
Panel
Modes:  1:1920x1080@60*!  2:1920x1080@48  3:1280x1024@60  4:1024x768@60
 5:1280x800@60  6:1920x1080@60  7:1600x900@60  8:1368x768@60  9:1280x720@60 
Geometry: 0,173 1920x1080
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: Automatic
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
Color profile source: sRGB
Color power preference: prefer efficiency and performance
Brightness control: supported, set to 100% and dimming to 100%
Output: 2 DP-1
enabled
connected
priority 1
DisplayPort
Modes:  10:3440x1440@60!  11:3840x2160@60  12:3840x2160@60 
13:3840x2160@50  14:3440x1440@120*  15:3440x1440@100  16:2560x1440@144 
17:1720x1440@60  18:1920x1080@120  19:1920x1080@120  20:1920x1080@60 
21:1920x1080@60  22:1920x1080@60  23:1920x1080@60  24:1920x1080@60 
25:1920x1080@50  26:1920x1080@50  27:1680x1050@60  28:1280x1024@75 
29:1280x1024@60  30:1440x900@60  31:1280x960@60  32:1152x864@75  33:1280x720@60
 34:1280x720@60  35:1280x720@60  36:1280x720@50  37:1024x768@75  38:1024x768@70
 39:1024x768@60  40:800x600@75  41:800x600@72  42:800x600@60  43:800x600@56 
44:720x576@50  45:720x480@60  46:720x480@60  47:720x480@60  48:720x480@60 
49:640x480@75  50:640x480@73  51:640x480@67  52:640x480@60  53:640x480@60 
54:640x480@60  55:720x400@70 
Geometry: 1920,0 2992x1253
Scale: 1.15
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: Full
HDR: disabled
Wide Color Gamut: disabled
ICC profile: none
Color profile source: sRGB
Color power preference: prefer efficiency and performance
Brightness control: supported, set to 100% and dimming to 100%
(base) [Riso@x ~]$

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

[okular] [Bug 501170] Editing pdf formt fields

2025-03-06 Thread Sune Vuorela

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

Sune Vuorela  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
 CC||k...@pusling.com

--- Comment #1 from Sune Vuorela  ---
This was fixed in 2023 in poppler.

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

[plasmashell] [Bug 501130] Clipboard history replaces non-Latin characters with an escape sequence

2025-03-06 Thread Daniil

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

Daniil  changed:

   What|Removed |Added

Version|unspecified |6.3.2
   Target Milestone|--- |1.0
   Assignee|unassigned-b...@kde.org |plasma-b...@kde.org
Product|kde |plasmashell
  Component|general |Clipboard widget & pop-up

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

[plasmashell] [Bug 493365] unable to change brightness via system tray panel after system locks

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

TraceyC  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=486072

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

[xdg-desktop-portal-kde] [Bug 501172] New: Save file dialog crashes immediately after becoming visible

2025-03-06 Thread Laura David Hurka

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

Bug ID: 501172
   Summary: Save file dialog crashes immediately after becoming
visible
Classification: Plasma
   Product: xdg-desktop-portal-kde
   Version: 6.3.2
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: laura.st...@mailbox.org
CC: aleix...@kde.org
  Target Milestone: ---

Application: xdg-desktop-portal-kde (6.3.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.11.0
Operating System: Linux 6.11.0-19-generic x86_64
Windowing System: Wayland
Distribution: KDE neon 6.3
DrKonqi: 6.3.2 [CoredumpBackend]

-- Information about the crash:
When I try to save a file from signal-desktop, this dialog crashes after about
a half second.

STEPS TO REPRODUCE
1. Click the download button on any file in signal-desktop.

ADDITONAL INFORMATION
Signal version, installed from snap:
signal-desktop7.44.0   764latest/stable 
snapcrafters✪  -

The crash can be reproduced every time.

-- Backtrace:
Application: xdg-desktop-portal-kde (xdg-desktop-portal-kde), signal: Aborted


This GDB supports auto-downloading debuginfo from the following URLs:
  
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.

warning: Can't open file /memfd:wayland-shm (deleted) during file-backed
mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing
[New LWP 39272]
[New LWP 39274]
[New LWP 39277]
[New LWP 39273]
[New LWP 39447]
[New LWP 39452]
[New LWP 39454]
[New LWP 39446]
[New LWP 39451]
[New LWP 39276]
[New LWP 39448]
[New LWP 39275]
[New LWP 39453]

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6StatusNotifierItem.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6KIOFileWidgets.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6KIOWidgets.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6WaylandClient.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6KIOGui.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6WindowSystem.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6Notifications.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6IconThemes.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6ConfigGui.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6Quick.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6Qml.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6KIOCore.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6I18n.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6Service.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6ConfigCore.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6CoreAddons.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6PrintSupport.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6Widgets.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6Gui.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6DBus.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6Core.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6IconWidgets.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6BookmarksWidgets.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6GuiAddons.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6Solid.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6Bookmarks.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6Xml.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libKF6WidgetsAddons.so.6

warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libQt6Network.so.6

warning: could not find '.gnu_debugaltlink' file for

[plasmashell] [Bug 497794] Powerdevil randomly changes brightness by 10% instead of 5% using brightness keys after waking the system

2025-03-06 Thread Jakob Petsovits

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

Jakob Petsovits  changed:

   What|Removed |Added

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

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

[xdg-desktop-portal-kde] [Bug 501172] Save file dialog crashes immediately after becoming visible

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

Bug Janitor Service  changed:

   What|Removed |Added

   Sentry Crash||https://crash-reports.kde.o
 Report||rg/organizations/kde/issues
   ||/112252/events/e599410f6ce3
   ||48559db6ef8b1eaa8ecf/

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

[plasmashell] [Bug 500448] plasmashell crash on login

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

--- Comment #3 from Bug Janitor Service  ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it will be automatically closed as
RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read
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 499658] Crash when closing a playing animation while more than 1 document tab is open

2025-03-06 Thread Emmet O'Neill

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

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com
 CC||emmetoneill@gmail.com

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

[plasmashell] [Bug 500903] In LibreOffice Writer, DdeLink bookmarks are created in the document when copying text to the clipboard

2025-03-06 Thread Fushan Wen

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

Fushan Wen  changed:

   What|Removed |Added

  Component|wayland-generic |Clipboard widget & pop-up
Product|kwin|plasmashell
   Target Milestone|--- |1.0
   Assignee|kwin-bugs-n...@kde.org  |plasma-b...@kde.org

--- Comment #7 from Fushan Wen  ---
(In reply to tux from comment #6)
> That's on MacOS when running the MacOS program "Keyboard Maestro", so not
> relevant here on Linux.

It's actually the same "bug" (expected behavior) because both have the
clipboard manager feature.

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

[kwin] [Bug 500819] SDDM / Desktop is not reachable since 6.3.2 with multiple monitors configuration

2025-03-06 Thread Kai Krakow

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

Kai Krakow  changed:

   What|Removed |Added

 CC||k...@kaishome.de

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

[kdeconnect] [Bug 422136] Album art gets sent from the computer to the phone, but not the other way round

2025-03-06 Thread Unknown

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

kel...@yahoo.com  changed:

   What|Removed |Added

 CC||kel...@yahoo.com

--- Comment #7 from kel...@yahoo.com  ---
Which Android and desktop versions of KDE Connect are needed for this feature
to work? I'm on desktop version 24.12.3 and Android version 1.32.11. This
feature is not working for me.

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

[plasmashell] [Bug 501169] New: Plasma desktop may crash when plug/unplug external display

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

Bug ID: 501169
   Summary: Plasma desktop may crash when plug/unplug external
display
Classification: Plasma
   Product: plasmashell
   Version: 6.3.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: joey.joey...@gmail.com
  Target Milestone: 1.0

SUMMARY
Sometimes, connecting a monitor via HDMI may cause Plasma to crash as it
attempts to move the main display from the laptop screen to the external
display.

STEPS TO REPRODUCE
Before reproducing, make sure the external monitor is set as the main display
and the laptop screen set to turn off automatically when monitor is connected
1. Connect external monitor to laptop (HDMI port, idk if this affects DP)
2. Laptop display will turn off, and screen will appear on external monitor

OBSERVED RESULT
Plasma desktop disappears (background turns black, taskbar, desktop icons, and
widgets disappear)
Only kwin remains running
(Same thing happens when going from external monitor back to laptop display)

EXPECTED RESULT
Desktop should switch displays successfully without crashing

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 2 × AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G
Memory: 7.2 GiB of RAM
Graphics Processor: AMD Radeon R5 Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 3180
System Version: 1.1.0
Monitor: Gigabyte GS27Q

ADDITIONAL INFORMATION
Does not happen every time, may take a few attempts for this to happen

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

[kwin] [Bug 501168] New: Screen flickering and artifacts when waking up from sleep with AMD GPU

2025-03-06 Thread Andrea Ippolito

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

Bug ID: 501168
   Summary: Screen flickering and artifacts when waking up from
sleep with AMD GPU
Classification: Plasma
   Product: kwin
   Version: 6.3.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: andrea.i...@gmail.com
  Target Milestone: ---

Hi,

this is related to:
https://gitlab.freedesktop.org/drm/amd/-/issues/4009

As per Mario's recommendation, I'm also opening a report here, although my
layman instincts suggest that something's wrong on the AMD side of things.

My framework laptop 13 with an AMD 7840U chip behaves unpredictably after
waking up from sleep. At times everything works fine, other times it spirals
down into freezes that force me to power off and start from scratch. Those
freezes are usually preceded by blocky artifacts or kwin animations repeating
in loop, like minimizing a window.

System info:

Operating System: openSUSE Tumbleweed 20250304
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3-1-default (64-bit) -> linux-firmware-amdgpu is 20250206
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon  780M Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

If you don't mind I would keep attachments in the aforementioned ticket on the
freedesktop drm/amd project, to avoid duplicates. If you do mind, please let me
know and I'll make sure to upload my attachments/logs in both tickets.

Thanks

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

[krunner] [Bug 474981] Searching for "shutdown", "restart" or "sleep" brings up the "Desktop Session" KCM instead of performing the actions themselves

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

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

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

[krunner] [Bug 474981] Searching for "shutdown", "restart" or "sleep" brings up the "Desktop Session" KCM instead of performing the actions themselves

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[dolphin] [Bug 500709] When entering an smb:// url, the first colon ':' keystroke is ignored

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

--- Comment #2 from n...@xoorg.org ---
It does happen with sftp:// URLs as well.  Admittedly, it appears to be
intermittent -- I don't have a reliable way to reproduce this.

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

[kcalc] [Bug 501000] Using the square root function in science mode leads to "Malformed expression"

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

p...@lsi.bas-net.by changed:

   What|Removed |Added

 Resolution|NOT A BUG   |FIXED

--- Comment #2 from p...@lsi.bas-net.by ---
Previously, the root and other functions were calculated from the displayed
content of the input field, why not return exactly this behavior. If there are
no brackets, then it is obvious. Well, or add a check for switching?

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

[digikam] [Bug 500239] Face tags from iPhone cannot overwriiten or deleted

2025-03-06 Thread Rainer Giese

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

Rainer Giese  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|FIXED   |---

--- Comment #3 from Rainer Giese  ---
I have now installed the 8.6-PreRelease (version from 2025-03-06 06:19) , but
it crashes during starting.
I still can answer the retraining question for the face database, and a few
seconds after then digikam closes all eyes.
If I skip all the entry questions, digikam not crashes, but the behavour with
the presetted face tags from iPhone is still the same.

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

[frameworks-kwallet] [Bug 501135] New: Kwallet crash if you don't accept the crypt type

2025-03-06 Thread Daniele Scasciafratte

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

Bug ID: 501135
   Summary: Kwallet crash if you don't accept the crypt type
Classification: Frameworks and Libraries
   Product: frameworks-kwallet
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: mte90...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY
So few days ago it seems that kwallet reset it (I lost all the db saved but I
can recover it from another computer) and I got a wizard asking me to set the
password for the database.
I closed it instead to continue and for few days I got a lot of crash (that I
sent) but today I was very bored and started thinking what happened and I
remembered.
I tried running kwalletd on console to see what is happening:

```
kwalletd6: ./src/runtime/kwalletd/kwalletd.cpp:603: int
KWalletD::internalOpen(const QString&, const QString&, bool, WId, bool, const
QString&): Assertion `b->cipherType() != KWallet::BACKEND_CIPHER_UNKNOWN'
failed.
KCrash: Application 'kwalletd6' crashing... crashRecursionCounter = 2
```

So I closed the kwalletd process, put a kwallet.kwl file that I backupped years
ago and now the issue gone.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.3.1
KDE Plasma Version: 
KDE Frameworks Version: 24.12
Qt Version: 6

ADDITIONAL INFORMATION

I am on debian sid

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

[krunner] [Bug 500972] Feature Request: rank search results by frequency

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

--- Comment #2 from ins...@no.capfr.fr ---
Created attachment 179170
  --> https://bugs.kde.org/attachment.cgi?id=179170&action=edit
screenshot of plasma search settings

(In reply to Nate Graham from comment #1)
> This is just the standard KRunner-provided search; moving to KRunner.
> 
> Can you attach a screen recording that shows the issue happening?
> 
> And then can you also attach a screenshot showing the state of System
> Settings > Search > Plasma Search?

Hello Nate, thank you for your reply.
here's a video of me trying to start Discord from the search bar:
https://youtu.be/UMAdwr6c5xM
I hope the attachment thing works for the screenshot.

Please do note that this is a feature request and not a bug report. I'm sure
this is behaving as intended, I just think the intention should be configurable
to make the search results more suited to my needs.

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

[systemsettings] [Bug 500967] Feature Request: Disable keyboard shortcuts

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

--- Comment #2 from ins...@no.capfr.fr ---
(In reply to Nate Graham from comment #1)
> If something has default shortcuts, those can be disabled rather than
> removed, yes. Non-default shortcuts can only be removed though. And for
> custom commands, since they by definition have no default shortcuts, they
> therefore inherit the "can only be deleted, not disabled" behavior. So I can
> see where the issue comes from with your use case.
> 
> The thing is, if we did add the functionality you're requesting, surely the
> "this is a pain in the ass" behavior would simply shift to the annoyance of
> having to disable and re-enable the shortcut. It wouldn't actually stop
> being a pain in the ass, right?
> 
> In general, since the shortcuts are global in scope, you want to avoid
> overlaps with apps' functionality. Generally that's accomplished by using
> modifier keys. In this case, maybe Meta+F10 would be a better shortcut? Is
> there a reason why that doesn't work for your use case?

Hi Nate, thank you for your reply.
Indeed, the pain in the ass behaviour would shift to the need for enabling and
disabling custom shortcuts, but the underlying issue that keycodes are
intercepted and not forwarded to the active application is as far as I
understand a fundamental core part of waylands  ̶d̶e̶g̶r̶a̶d̶a̶t̶i̶o̶n̶ ̶o̶f̶ 
̶u̶s̶e̶r̶ ̶e̶x̶p̶e̶r̶i̶e̶n̶c̶e̶
security tenets, so that cannot be changed. It is still preferable (in my
opinion) to be able to enable and disable custom shortcuts instead of having to
keep track of custom shortcuts in a spreadsheet somewhere that is separate from
the KDE settings.
The reason why Meta+F10 does not work for my case is twofold: 1) It's probably
already bound to some default shortcut like "Switch to Workspace 10" and 2) I
have a 65% keyboard that doesn't have a function-key row. Not only do I not
have a Meta button on the right side of my keyboard, I also need to hit the
Layer+ key to turn my Number-Row into the function row, and suddenly a 2-button
shortcut is turned into a 3-button shortcut not unlike the 3-finger salute,
just even more uncomfortable.

You are of course not obligated in any way to support custom keyboard layouts,
this is just the reason why for me personally it doesn't work well.

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

[krita] [Bug 501128] Unknown Error message when canceling export and overwrite

2025-03-06 Thread Halla Rempt

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

Halla Rempt  changed:

   What|Removed |Added

 CC||ha...@valdyas.org
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Halla Rempt  ---
Yes, something is wrong here.

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

[kdevelop] [Bug 486949] Kdevelop freezes after git checkout feature-branch

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

--- Comment #12 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/735

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

[plasmashell] [Bug 499893] No fingerprint auth option when laptop wakes from sleep

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

jami.pcwps...@m.krakow.pl changed:

   What|Removed |Added

 CC||jami.pcwps...@m.krakow.pl

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

[plasmashell] [Bug 500037] Weird playback control behavior while unpinning an icon in Plasma panel

2025-03-06 Thread Angad

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

Angad  changed:

   What|Removed |Added

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

--- Comment #8 from Angad  ---
Somehow it got fixed so not an issue now

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

[kwin] [Bug 402857] dfdsfs

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

Mp  changed:

   What|Removed |Added

 CC||micahpowchperso...@gmail.co
   ||m
Summary|Touchpad and touchscreen|dfdsfs
   |gestures should be  |
   |configurable|

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

[okular] [Bug 424798] Standard double click and drag text selection to select words, triple click to select whole lines

2025-03-06 Thread pallaswept

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

pallaswept  changed:

   What|Removed |Added

 CC||pallasw...@proton.me

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

[plasmashell] [Bug 501133] New: Three finger swipe up for app reveal does not work, while four finger swipe does work. Ultimately, there should be a settings GUI for configuring touchpad swipe actions

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

Bug ID: 501133
Summary: Three finger swipe up for app reveal does not work,
while four finger swipe does work. Ultimately, there
should be a settings GUI for configuring touchpad
swipe actions.
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: "Manage Desktop and Panels" window
Assignee: plasma-b...@kde.org
Reporter: micahpowchperso...@gmail.com
Target Milestone: 1.0

Created attachment 179169
--> https://bugs.kde.org/attachment.cgi?id=179169&action=edit
The overview application pager that a three finger swipe up should open

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

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
While four finger gestures work wonderfully, just like mac, in KDE Plasma on
Wayland, three finger gestures do not open the app overview. They only page
desktops left and right. This is very important for me, because I have a small
trackpad and it is difficult to fit all four of my fingers on it in order to
swipe up. This renders swiping up useless for me. I would love to use the swipe
up feature as easily as I can on mac. And if I can get that working, I would
fully commit to linux. Right now, I still want a mac. This should not be a
difficult fix. Yall already got it working for four fingers! Three fingers is
even less fingers! Please implement this when you get the chance :P

STEPS TO REPRODUCE
1. Wayland. Arch. KDE Plasma.
2. Place four fingers on the trackpad
3. Move them up simyltaneously.
4. WOW
5. Place three fingers on the trackpad
6. Move them up simyltaneously
7. Post a bug report on kde.org about it and then cry myself to sleep.

OBSERVED RESULT
No window expose

EXPECTED RESULT
Window expose

SOFTWARE/OS VERSIONS
Windows:
macOS:
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Arch. Wayland
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Boom

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

[plasmashell] [Bug 501133] Three fingers swipe up should open app overview. It does not. Only four fingers opens app overview. :( Unusable on my small trackpad. (Ultimately, there should be a configur

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

Mp  changed:

   What|Removed |Added

Summary|Three finger swipe up for   |Three fingers swipe up
   |app reveal does not work,   |should open app overview.
   |while four finger swipe |It does not. Only four
   |does work. Ultimately,  |fingers opens app overview.
   |there should be a settings  |:( Unusable on my small
   |GUI for configuring |trackpad. (Ultimately,
   |touchpad swipe actions. |there should be a
   ||configuration settings page
   ||for trackpad gestures,
   ||please)

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

[dolphin] [Bug 501134] New: Duplicate Open terminal entry in right click menu if the ghostty terminal is set as default

2025-03-06 Thread Angad

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

Bug ID: 501134
   Summary: Duplicate Open terminal entry in right click menu if
the ghostty terminal is set as default
Classification: Applications
   Product: dolphin
   Version: 24.12.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: angxdd...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 179171
  --> https://bugs.kde.org/attachment.cgi?id=179171&action=edit
Right click menu

SUMMARY
So I have been using ghostty terminal and I have heard it's native so even when
it's not set as default terminal It still appears in the right click menu in
dolphin, but the issue is once I set ghostty as default terminal still there
are two entries in the right click menu as:-
~Open terminal here 
~Open Ghostty here

but both these open ghostty terminal and the 1st option has konsole logo
instead of ghostty while the open terminal here entry also opens ghostty
terminal as ghossty is default I think it shouldn't show two entries in dolphin
once ghostty is set as default 



SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.3.2
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2

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

[kwin] [Bug 402857] Touchpad and touchscreen gestures should be configurable

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

Mp  changed:

   What|Removed |Added

Summary|dfdsfs  |Touchpad and touchscreen
   ||gestures should be
   ||configurable

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

[dolphin] [Bug 472040] Wayland: Right-clicking on the columns while the window is not in focus makes the context menu appear in its own window

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

Naxdy  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from Naxdy  ---
Not a problem anymore.

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

[okular] [Bug 472041] Wayland: Clicking the "View Mode" button while the window is unfocused makes the context menu appear in its own window

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

Naxdy  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from Naxdy  ---
Not a problem anymore.

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

[kwin] [Bug 501137] New: GTK appmenus initially open in the wrong position until moving the cursor over a different menu entry

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

Bug ID: 501137
   Summary: GTK appmenus initially open in the wrong position
until moving the cursor over a different menu entry
Classification: Plasma
   Product: kwin
   Version: 6.3.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: xna...@hydra-development.net
  Target Milestone: ---

Created attachment 179173
  --> https://bugs.kde.org/attachment.cgi?id=179173&action=edit
Bug showcase

SUMMARY
GTK appmenus initially open in the wrong position until moving the cursor over
a different menu entry (see attached video)

STEPS TO REPRODUCE
1. Open an affected GTK app (tested with DBeaver and KiCad)
2. Click on an appmenu item that isn't the first
3. Move the mouse over to a different appemenu item

OBSERVED RESULT
Appmenu opens under the first menu entry initially ("File"), then updates to
the current menu entry once hovering over a different entry.

EXPECTED RESULT
Appmenu opens initially under the menu entry that is being hovered over during
the click, then updates to the new menu entry once hovering over a new one.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-zen1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 3950X 16-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor 1: AMD Radeon RX 7900 XTX
Graphics Processor 2: llvmpipe

ADDITIONAL INFORMATION
-

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

[krdc] [Bug 319244] The "current resolution" setting is saved, but if the monitor resolution changes, the setting does not reflect this change

2025-03-06 Thread Fabio

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

Fabio  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/netw
   ||ork/krdc/-/commit/5928fed49
   ||0de05c16c6974553b70a0723c21
   ||ee50
 CC||ctrlal...@gmail.com
   Version Fixed In||24.05
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

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

[gcompris] [Bug 501140] New: Too small amount of money in change-money exercise availlable

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

Bug ID: 501140
   Summary: Too small amount of money in change-money exercise
availlable
Classification: Applications
   Product: gcompris
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jaz...@gmail.com
  Reporter: ulrich.li...@jaw.at
  Target Milestone: ---

Created attachment 179176
  --> https://bugs.kde.org/attachment.cgi?id=179176&action=edit
Screenshot of exercise with too little money to pay

SUMMARY
In the German version of the exercise "Give Tux his change, including cents"
you can see in the screenshot, that the overall price of the goods is 7,15 €.
But the maximum amount available, you can select, is 7,09 €. So with this bug,
the exercise is unsolveable.

The error has occured at level 4 of this exercise.
Though being a clear error evidenced with a screenshot, it was not
reproducable.
Nevertheless, there must be a flaw, maybe in the calculation algorithm

STEPS TO REPRODUCE
-

OBSERVED RESULT
Only 7,09 € are availlable in the excercises money-pool, while the demanded
overall-amount is 7,15 €

EXPECTED RESULT
That at least the same amount demanded was available in the money-pool, so at
least 7,15 € here

SOFTWARE/OS VERSIONS
Software:
GCompris for Linux, Version 4.3

OS:
Linux --> Debian-based distro Emmabuntüs, Version DE5 1.03


ADDITIONAL INFORMATION

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

[systemsettings] [Bug 501057] New EU regulations coming into force in May requires warnings when disabling power management features

2025-03-06 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/powerdevil/-/commit/2660 |ma/powerdevil/-/commit/f9ee
   |49c40a637ae2a814ce6c602fcec |024a2ea5cf9ac25ecc3ae05f077
   |dc65fa85b   |c845f82b9

--- Comment #6 from Kai Uwe Broulik  ---
Git commit f9ee024a2ea5cf9ac25ecc3ae05f077c845f82b9 by Kai Uwe Broulik.
Committed on 06/03/2025 at 06:25.
Pushed by broulik into branch 'Plasma/6.3'.

kcm: Show warning when disabling autosuspend or setting it too long

EU Regulation 2023/826 requires connected devices to auto-suspend
after at most 20 minutes. The user may disable this but a warning
has to be presented when they do.

The warning is only shown when changing the setting, not when it
has already been changed before.


(cherry picked from commit 266049c40a637ae2a814ce6c602fcecdc65fa85b)

Co-authored-by: Kai Uwe Broulik 

M  +27   -1kcm/ui/ProfileConfig.qml

https://invent.kde.org/plasma/powerdevil/-/commit/f9ee024a2ea5cf9ac25ecc3ae05f077c845f82b9

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

[kwin] [Bug 501137] GTK appmenus initially open in the wrong position until moving the cursor over a different menu entry

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

Naxdy  changed:

   What|Removed |Added

   Keywords||regression

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

[plasmashell] [Bug 501144] New: plasmashell keeps crashing repeatedly.

2025-03-06 Thread Rafael

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

Bug ID: 501144
   Summary: plasmashell keeps crashing repeatedly.
Classification: Plasma
   Product: plasmashell
   Version: 6.3.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: rafael.p.liberat...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.3.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.11.0
Operating System: Linux 6.13.5-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.3.2 [CoredumpBackend]

-- Information about the crash:
I just logged in, and Plasma keeps showing crash dialogs, even when the desktop
is idle with nothing open at all.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x711b738a56d3 in __pthread_kill_internal (threadid=,
signo=6) at pthread_kill.c:89
#7  0x711b7384bba0 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x711b73833582 in __GI_abort () at abort.c:73
#9  0x711b76a0f734 in wl_abort (fmt=fmt@entry=0x711b76a147f0 "Tried to add
event to destroyed queue\n") at ../wayland-1.23.1/src/wayland-util.c:476


Reported using DrKonqi

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

[plasmashell] [Bug 501030] KDE Plasma built-in Klipper saves clipboard history to Disk and only clears them on exit

2025-03-06 Thread Fushan Wen

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

Fushan Wen  changed:

   What|Removed |Added

Summary|KDE Plasma built-in Klipper |KDE Plasma built-in Klipper
   |saves clipboard history to  |saves clipboard history to
   |Disk and settings hardening |Disk and only clears them
   |don't do disable this   |on exit
   |behavior|

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

[plasmashell] [Bug 498593] Laptop goes into (broken) standby, if lid is closed during shut down

2025-03-06 Thread Vinícius

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

Vinícius  changed:

   What|Removed |Added

 CC||viniciush@gmail.com

--- Comment #2 from Vinícius  ---
you can workaround this issue putting 
'[Login]
HandleLidSwitch=ignore'
on /etc/systemd/logind.conf, so i'm guessing, would this be fixed if kde by
taking the handle-lid-switch inhibitor? as said in the logind.conf manpage 
"A different application may disable logind's handling of system power and
sleep keys and the lid switch by taking a low-level inhibitor lock
("handle-power-key", "handle-suspend-key", "handle-hibernate-key",
"handle-lid-switch", "handle-reboot-key"). This is most commonly used by
graphical desktop environments to take over suspend and hibernation handling,
and to use their own configuration mechanisms. If a low-level inhibitor lock is
taken, logind will not take any action when that key or switch is triggered and
the Handle*= settings are irrelevant."

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

[kwin] [Bug 501094] Freeze when selecting "Prefer color accuracy"

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

--- Comment #3 from riso...@gmail.com ---
(In reply to risocig from comment #2)
> (In reply to Zamundaaa from comment #1)
> > > The computer got frozen/very slow, after 15 seconds the setting did NOT 
> > > revert back
> > KScreen does revert this setting automatically, maybe something went wrong
> > with that.
> > 
> > Please reproduce the issue, and attach the outputs of
> > > kscreen-doctor -o
> > > journalctl --user-unit plasma-kwin_wayland --boot 0
> > > sudo dmesg
> > and
> > > drm_info
> > here
> 
> Hello, I dont have drm_info command
> (base) [Riso@x ~]$ drm_info
> bash: drm_info: command not found

It is this right? https://aur.archlinux.org/packages/drm_info
I will install it and send the result

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

[krdc] [Bug 465649] Default credentials for RDP connections

2025-03-06 Thread Fabio

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

Fabio  changed:

   What|Removed |Added

 CC||ctrlal...@gmail.com
 Resolution|--- |WORKSFORME
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Fabio  ---
There are no sufficient information in this ticket to understand what's going
on.

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

[Discover] [Bug 491328] Discover Flatpak updates for applications are listed as "Refresh of version X"

2025-03-06 Thread John Veness

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

--- Comment #14 from John Veness  ---
(In reply to Paul B. from comment #13)
> John, if that were so, that actual updates had been made, then wouldn't
> other package handlers offer the updates as such? That hasn't been happening
> here.

Assuming you mean the updates aren't showing up in Synaptic or MX Package
Installer, I don't know about MX Package Installer but Synaptic only shows apt
updates, not flatpaks.

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

[plasmashell] [Bug 500951] KDE PowerDevil deadlock causes kwin_wayland to hang

2025-03-06 Thread Jona Wagner

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

--- Comment #3 from Jona Wagner  ---
I did some more debugging (coredump available if needed)

the Display Lock Record of libddcutil has this data:
(gdb) p dlr
$1 = (Display_Lock_Record *) 0x5b97091df140
(gdb) p *dlr
$2 = {marker = "DDSC", io_path = {io_mode = DDCA_IO_I2C, path = {i2c_busno = 4,
hiddev_devno = 4}}, display_mutex = {p = 0x1, i = {1, 0}}, display_mutex_thread
= 0x7602b8000de0, linux_thread_id = 20887}

The noted linux_thread_id is still active, the backtrace follows:
```
(gdb) thr 2
[Switching to thread 2 (Thread 0x7602c5ffb6c0 (LWP 20887))]
#0  __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
56  ret
(gdb) bt
#0  __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x7602e7a9fe33 in __internal_syscall_cancel (a1=,
a2=, a3=, a4=, a5=a5@entry=8,
a6=a6@entry=0, nr=271) at cancellation.c:49
#2  0x7602e7a9fe74 in __syscall_cancel (a1=, a2=, a3=, a4=, a5=a5@entry=8, a6=a6@entry=0,
nr=271) at cancellation.c:75
#3  0x7602e7b1aa06 in __GI_ppoll (fds=fds@entry=0x5b9709222c90,
nfds=nfds@entry=1, timeout=, timeout@entry=0x0,
sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42
#4  0x7602e689f6a7 in ppoll (__fds=0x5b9709222c90, __nfds=1, __timeout=0x0,
__ss=0x0) at /usr/include/bits/poll2.h:101
#5  g_main_context_poll_unlocked (priority=,
context=0x7602b8000c40, timeout_usec=, fds=0x5b9709222c90,
n_fds=1) at ../glib/glib/gmain.c:4591
#6  g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7602b8000c40, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4268
#7  0x7602e683be15 in g_main_context_iteration (context=0x7602b8000c40,
may_block=1) at ../glib/glib/gmain.c:4338
#8  0x7602e77c575d in QEventDispatcherGlib::processEvents
(this=0x7602b8001010, flags=...) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:399
#9  0x7602e75606a6 in QEventLoop::processEvents (this=0x7602c5ffaa70,
flags=...) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventloop.cpp:103
#10 QEventLoop::exec (this=0x7602c5ffaa70, flags=...) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventloop.cpp:185
#11 0x7602e7657999 in QThread::exec (this=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread.cpp:590
#12 QThread::run (this=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread.cpp:711
#13 0x7602e76d8a9b in operator() (__closure=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:375
#14 (anonymous
namespace)::terminate_on_exception >
(t=...) at
/usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:311
#15 QThreadPrivate::start (arg=0x7602d801f188) at
/usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:339
#16 0x7602e7aa370a in start_thread (arg=) at
pthread_create.c:448
#17 0x7602e7b27aac in __GI___clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
```

I also checked the callback thread
Mar 02 10:30:14 r9950 org_kde_powerdevil[1989]: [ 20885] libddcutil callback
thread 0x7602bc002e00 started

while the thread meta information still resides in memory
```
(gdb) p *(GThreadPosix*)0x7602bc002e00 
$11 = {thread = {thread = {func = 0x7602e6ce4980 ,
data = 0x7602bc002a40, joinable = 1, priority = G_THREAD_PRIORITY_LOW},
ref_count = 1, ours = 1, name = 0x0, retval = 0x0}, 
  system_thread = 129754267096768, joined = 0, lock = {p = 0x0, i = {0, 0}},
proxy = 0x7602e6871f10 }
(gdb) p (pthread_t*) 129754267096768
$13 = (pthread_t *) 0x7602c4ff96c0
```
the thread is no longer running
```
(gdb) info thr
  Id   Target Id Frame 
  1Thread 0x7602df5c4ac0 (LWP 1989)  __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
* 2Thread 0x7602c5ffb6c0 (LWP 20887) __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
  3Thread 0x7602dc9fa6c0 (LWP 2023)  __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
  4Thread 0x7602dd1fb6c0 (LWP 2022)  __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
  5Thread 0x7602dd9fc6c0 (LWP 2021)  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7602de1fd6c0 (LWP 2020)  __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
  7Thread 0x7602de9fe6c0 (LWP 2019)  __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
  8Thread 0x7602df1ff6c0 (LWP 2005)  __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
```

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

[plasmashell] [Bug 500478] Screen locker sometimes only shows black screen after unlocking with password when fingerprint reader is available

2025-03-06 Thread postix

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

postix  changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[kwin] [Bug 501149] New: System Settings Keyboard Shortcut Page opening automatically when launching Brave Browser

2025-03-06 Thread Engin Karakurt

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

Bug ID: 501149
   Summary: System Settings Keyboard Shortcut Page opening
automatically when launching Brave Browser
Classification: Plasma
   Product: kwin
   Version: 6.3.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: street4...@proton.me
  Target Milestone: ---

SUMMARY
I installed Fedora 41 KDE on my PC. After updating the system and rebooting, I
installed Brave Browser using their installation steps for Fedora 41+ (See
attachment screenshot for their steps). I then went into the brave://flags
section and set the "Preferred Ozone platform" to Auto so that I can use
Wayland (Which avoids issues with the Window for me). After doing that
everything works fine, except for one thing. When I start the Brave Browser
Application, it will always open the System Settings Shortcuts Page
automatically, even though nothing prompted it to do so. This only happens when
I set it to use Wayland, not on the Default setting. It did not happen on
Plasma 6.3.1 (currently using 6.3.2). I am not 100% sure if this bug belongs to
kwin, sorry if this is the wrong category.

STEPS TO REPRODUCE
1. Install Brave Browser
2. Go into the brave://flags section and set the "Preferred Ozone platform" to
Auto so that Brave uses Wayland instead of X11 
3. Restart Brave Browser

OBSERVED RESULT
The Keyboard Shortcut Settings Page opens together with Brave Browser and takes
focus

EXPECTED RESULT
Only Brave Browser should open, no Keyboard Shortcut Settings Page

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 41 KDE
KDE Plasma Version: 6.3.2 
KDE Frameworks Version: 6.11.0 
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Kernel Version: 6.13.5-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2
Using the RPMFusion Nvidia Driver

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

[kwin] [Bug 501145] key is buffered if released after modifier