date:20250221

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

Bug ID: 500509
   Summary: Device names are cut off in the Energy view in
kinfocenter
Classification: Applications
   Product: kinfocenter
   Version: 6.3.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: aron...@gmail.com
CC: sit...@kde.org
  Target Milestone: ---

Created attachment 178681
  --> https://bugs.kde.org/attachment.cgi?id=178681&action=edit
energy_view_screenshot

If a device's default name is longer (like "Microphone headphones") it will
overflow the card in the Energy statistics view.

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.12.13-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland

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

[plasmashell] [Bug 483163] Sometimes on X11 with compositing turned on, black lock screen when using Breeze Plasma style, but controls are all there and remain interactive

2025-02-21 Thread Roman

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

--- Comment #123 from Roman  ---
I am on latest Arch, Plasma 6.3.1.1, and still have black screen with cursor
after resuming from sleep on x11 session. (does not happen on wayland).

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

[krunner] [Bug 500493] KRunner doesn’t respond to shortcuts

2025-02-21 Thread Andrija

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

--- Comment #2 from Andrija  ---
Got it! Thanks for letting me know.

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

[konsole] [Bug 500364] bold font

2025-02-21 Thread Filip

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

Filip  changed:

   What|Removed |Added

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

--- Comment #8 from Filip  ---
Thanks for checking. Then, there is no problem with Konsole so I would close
this ticket.

As for your problem, you can search for the bold version of the Monospace font,
and if you don't find it, use some other font (that has bold version) that is
similar to that one.

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

[krunner] [Bug 500510] KRunner fails to open via shortcut after first time/first minute.

2025-02-21 Thread Antonio Rojas

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

Antonio Rojas  changed:

   What|Removed |Added

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

--- Comment #1 from Antonio Rojas  ---


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

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

[plasma-integration] [Bug 500435] "Open Folder" (directory picker) does not save the sidebar width

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kinfocenter] [Bug 500412] The Hardware section of the Info Center shows wrong size values for 'Memory' on its initial (summary) page

2025-02-21 Thread John

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

--- Comment #8 from John  ---
(In reply to Nate Graham from comment #4)
> We're just showing the truth here. The marketing tricks are unfortunate, but
> we don't have any control over them.
First, no, you're not showing the truth here!
The only truth shown here is the unit, being GiB, which is correct.
The value is not the truth as the calculation is wrong, it doesn't take all the
memory already reserved (used) to reach the proper total!

JEDEC is a standardization organization that mandates the use of binary (base
2) to calculate the values of sizes.
On the unit notation it uses (recommends) 3 prefixes: K, M and G.
K being 1024 (2 to the 10th power)
M being  K to the power of 2, where K = 1024.
G being  K to the power of 3, where K = 1024.
A standard that we have since 2002:
https://en.wikipedia.org/wiki/JEDEC_memory_standards#JEDEC_Standard_100B.01
We are lucky that all RAM manufacturers, without exception, follow the JEDEC
standard!
Maybe because all programming languages and programmers work with bits and
bytes (base 2) and everything would be a mess and a nightmare with the base 10
that doesn't aling nicely.
And it's not only RAM manufacturers that either follow the JEDEC standard or
just binary units without any relation to JEDEC, but also CPU GPU and hard
drive manufacturers when it comes to chaches sizes.
While it's harder to get a confirmation after a few searches for the chaches
sizes, I think the "Where used (mainly)" part of this answer confirms it:
https://cseducators.stackexchange.com/a/4446
And these 2 answers confirms it for the RAM sizes only:
https://www.reddit.com/r/explainlikeimfive/comments/13sc135/comment/jloxsvx/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
https://www.reddit.com/r/explainlikeimfive/comments/13sc135/comment/jloykan/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

UEFI / BIOSes seem to follow the JEDEC standard too, except that hey prefer to
show MB instead of just M as recommended in the standard:
How UEFI / BIOSes is showing it -> 8192 MB + type + frequency:
https://4.bp.blogspot.com/-aOQT-q1cVnk/VTIU5qb2kqI/GWk/z2Rt2NWWXJg/s1600/20645-01-asus-uefi-11380626.jpg
https://www.ocinside.de/media/uploads/asrock_b450m_steel_legend_uefi_1.jpg

So, when it comes to physical RAM sticks, for which I opened this bug report,
the RAM sticks manufacturers (vendors) + marketers + UEFI / BIOS manufacturers
never lie as they count in base 2 (of course with the exception of the units
which are a bit wrong, showing MB or GB when JEDEC recommends M and G and IEC
recommends MiB and GiB).

The ones that clearly lie / trick you, are the hard drive manufactures which
prefer to use base 10, so K being 1000 instead of 1024, when it comes to the
big, non-cache part.
They can even rob / trick you of a whopping 2 TiB when they sell you a 22 TB
hard drive:
https://duckduckgo.com/?t=ffab&q=22+TB+in+TiB&ia=web
But still there, the small 256 or 512 chaches they come with should be MiB and
not MB.

And then there are also the networking equipment manufacturers that lie / trick
you, that are even worse than the hard drive manufacturers as they use bits
instead of bytes, so their numbers are not only 1.024 bigger like hard drive
manufacturers show, but a whopping 8 times.
A 100 Mb/s being in reality just 12.5 MiB/s.
You get the idea how much different is for 1,000 of for 5,000 Mb/s connections.

> Our options are:
> 1. Show the truth and confuse people who both care about technical details
> and also don't know about how marketers lie about memory and storage
> capacities (i.e. that "256 GB SSD" never exposes 256GB of space to the OS;
> it's the same with memory)
> 2. Lie like the marketers do, and make people think they have more memory
> than they actually do, compared to the other places like Info Center where
> we have to show the truth for technical reasons.
>
> As such, I'm inclined to choose #1 and say this is intentional.
I'm also inclined to choose #1, to show the truth!
And for consistency and easier calculation just use the binary (base 2, so 2 to
some power) everywhere, not only the RAM memory sizes.
So also for storage and download / upload speeds.
For me it would be fine for connection speeds too, so 12.5 or 125 MiB/s.
But I also agree that for some consistency with the tricks in the real world,
that we cannot change, to also show those, like KDE Partition Manager does for
storage devices  or for networking equipment where people might know better the
100 / 1000 / 1 Gbps connections instead of the real binary speeds.

But the big problem here and why I opened this bug report is that the total
memory size is not shown correctly here.
It shows the allocatable / usable one!
I want to see the real one, the full / complete / total one, like the UEFI /
BIOS of the computer shows!
UEFI / BIOS, being much more low level than QT / KDE software and even than the
L

[kwin] [Bug 500511] New: Right-clicking on a scrollbar in Kwin debug console locks all input

2025-02-21 Thread Arttu

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

Bug ID: 500511
   Summary: Right-clicking on a scrollbar in Kwin debug console
locks all input
Classification: Plasma
   Product: kwin
   Version: 6.3.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: art...@pm.me
CC: duha.b...@gmail.com
  Target Milestone: ---

SUMMARY
Right-clicking on any scrollbar in Kwin debug console disables all mouse &
keyboard input (even the CTRL+ALT+F# combo to switch to a TTY!), forcing me to
SSH in from my phone to kill kwin_wayland.

STEPS TO REPRODUCE
1. Open kwin debug console
2. Switch to the OpenGL tab (or any tab with enough content to show a
scrollbar)
3. Right-click on the scrollbar

The context menu is opened but all input is permanently disabled.

SOFTWARE/OS VERSIONS
$ kinfo
Operating System: Arch Linux
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i9-9900K CPU @ 3.60GHz
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 7800 XT

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

[kate] [Bug 493665] kate losts session after restore plasma session

2025-02-21 Thread Waqar Ahmed

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

--- Comment #38 from Waqar Ahmed  ---
I fixed another Session related issue, so it might have fixed this as well. 

In any case, thanks for diligently testing. People rarely do that :)

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

[kinfocenter] [Bug 500412] The Hardware section of the Info Center shows wrong size values for 'Memory' on its initial (summary) page

2025-02-21 Thread John

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

--- Comment #9 from John  ---
I also looked a bit how others have decided to show it...

How Windows 7 is showing it -> 8.00 GB (7.75 GB usable) for 64-bit version:
https://2.bp.blogspot.com/_8qMdy9GxQw8/TTBBpquV2tI/Aro/BvfWmL2GmP8/s1600/windows-7-system-properties.gif
Or for 32-bit version, whith a big difference, probalby because it was
reserving a lot for the GPU:
https://i.ytimg.com/vi/2guGEiAUGNQ/maxresdefault.jpg
Or for 4 GiB 32-bit version:
https://www.groovypost.com/wp-content/uploads/2014/01/WEI-Tool-Windows-7.png

How Windows 10 is showing it -> 8.00 GB (7.85 GB usable):
https://i.imgur.com/gXfqa9f.png
https://www.javelin-tech.com/blog/wp-content/uploads/2020/03/find-computer-name.png
How Windows 11 is whowing it -> 8.00 GB (7.71 GB usable):
https://www.groovypost.com/wp-content/uploads/2021/09/1-Windows-11-About.png

How Android is showing it -> 3.9 GB/8GB used (and the reserved one on a new
line):
https://i.ytimg.com/vi/lfCp52y6UFU/maxresdefault.jpg
https://www.androidauthority.com/how-to-check-ram-in-android-3346256/

So Android tries to show everything on that page in a few lines, the available
one, the used one and the total one.
Since it can show the reserved one too, probably there the firmware and the
bootloader report to the OS how much they have reserved from it.
Unlike Windows that just shows the total one and leaves the used and available
one to other tools, like the task manager (resource / system monitor there).
Which makes sense when you have 2 different tools, one to show the system
information and one to should the resources usage.
Which Plasma has too, but I think this this information page is mingling
things, showing resource usages that belong to the System Monitor.
Even more since the hardware section should show the hardware as it is, not how
it is used or how much of it it is used.
For example the CPU in the same Hardware section is shown as:
8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Which besides the stupid 8 x (as as I have only one) is showing the correct
base frequency.
Not the current one which is only 400 MHz or the maximum one that sometimes is
reached, which is: 3.40 GHz:
https://www.intel.com/content/www/us/en/products/sku/124967/intel-core-i58250u-processor-6m-cache-up-to-3-40-ghz/specifications.html

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

[krunner] [Bug 480800] With NVIDIA GPU, on Wayland KRunner and other Plasma pop-ups are intermittently not opening with eglSwapBuffers errors

2025-02-21 Thread Antonio Rojas

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||henryc...@gmail.com

--- Comment #26 from Antonio Rojas  ---
*** Bug 500510 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen

2025-02-21 Thread Ultranium

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

--- Comment #74 from Ultranium  ---
(In reply to pditchev from comment #71)
> It may be a long shot, but is anyone else having keyboard issues at the same
> time? I'm having keys not react or trigger several times in some instances.
> Most likely it's a coincidence, but still.

Actually, I do have a similar problem.

When using Fedora 41 KDE spin in a KVM VM (virt-manager) with a SPICE display,
something strange happens.
Right after boot, everything works fine. Then, after a few times I switch in
and out of full-screen mode, key presses in KDE apps start to register funny:
when in full-screen mode, after pressing a key (in a Konsole for example) it is
not rendered. If I press another key, now both symbols are rendered. If I then
switch VM out of full-screen mode, then all key presses are handled just fine.
Going back to full-screen mode, the same problem appears.

What's interesting, typing within Firefox window works fine all the time, even
in a full-screen mode, so it doesn't look like a KVM/SPICE/virt-manager problem
to me.

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

[kate] [Bug 499311] Symbol Outline out of sync if file is reloaded

2025-02-21 Thread Waqar Ahmed

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

Waqar Ahmed  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/fram
   ||eworks/ktexteditor/-/commit
   ||/77cbafd60690de3cc7a6d8b333
   ||88501dd10257dc
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Waqar Ahmed  ---
Git commit 77cbafd60690de3cc7a6d8b33388501dd10257dc by Waqar Ahmed, on behalf
of Christoph Cullmann.
Committed on 21/02/2025 at 09:08.
Pushed by waqar into branch 'master'.

don't reset revision on reload but increment it

this avoids that we assume we are back to an old revision even
if the loaded text is totally different

M  +2-2autotests/src/katedocument_test.cpp
M  +5-4src/buffer/katetextbuffer.cpp
M  +3-4src/buffer/katetexthistory.cpp

https://invent.kde.org/frameworks/ktexteditor/-/commit/77cbafd60690de3cc7a6d8b33388501dd10257dc

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

[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen

2025-02-21 Thread Francisco

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

Francisco  changed:

   What|Removed |Added

 CC|franje...@gmail.com |

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

[systemsettings] [Bug 500151] Writes runtime configuration to /usr/share

2025-02-21 Thread David Redondo

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

--- Comment #16 from David Redondo  ---
Actually not, it is relative to theme dir
https://github.com/sddm/sddm/blob/c2b97dd63f726fa3db7f699bb40b2be3e62b8df5/src/greeter/GreeterApp.cpp#L109

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

[systemsettings] [Bug 500469] SDDM behaviour should not be under "Colours & Themes" settings

2025-02-21 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
>These behaviour settings which are not related to SDDM looks should be 
>somewhere under "Security & Privacy" or "System" (maybe even inside "Users" or 
>"Sessions").

Yeah, that's a valid point.
Out of curiosity, what settings were you changing. Autologin makes sense
elsewhere, probably under User.
The rest can probably just be deleted.

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

[systemsettings] [Bug 500469] SDDM behaviour should not be under "Colours & Themes" settings

2025-02-21 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |INTENTIONAL

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

[dolphin] [Bug 500381] Triggering a notification from Dolphin logs errors to the journal for qt.qpa.wayland

2025-02-21 Thread Akseli Lahtinen

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

Akseli Lahtinen  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Akseli Lahtinen  ---
Can confirm this warning, here's how I can repro it 

1. open dolphin in terminal, then open hamburger menu
2. go to create new and wait for the context menu to appear
3. right click the folder view
4. go to create new again

warning pops up

If you do steps 3 and 4 after restarting dolphin (and dont do 1,2)
the warning does not popup.

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.80
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.12.15-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600

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

[plasmashell] [Bug 500522] New: Shortcuts tool will not bind the control+pause key pair

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

Bug ID: 500522
   Summary: Shortcuts tool will not bind the control+pause key
pair
Classification: Plasma
   Product: plasmashell
   Version: 6.3.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Keyboard Layout widget
  Assignee: plasma-b...@kde.org
  Reporter: incan...@gmail.com
CC: butir...@gmail.com, duha.b...@gmail.com
  Target Milestone: 1.0

SUMMARY
The System Settings interface for editing keyboard shortcuts refuses to create
a shortcut for "cntrl+pause" (and potentially some other Cntrl+ combos as
well?). I have been using this key sequence to force a shutdown on my Windows
machine for years, so not having this available hurts my muscle memory.

When creating the mapping this failure is quite silent and hard to spot, it is
easy to end up remapping  alone accidentally because an attempt to map
+ has not done what you expected.

Specifically in the case of the cntrl+pause combination, the System Settings UI
will also-

1) Strip the cntrl+pause assignment out of the ~/.config/kglobalshortcutsrc
file if it has been edited in by hand
2) Strip a cntrl+pause assignment out of a custom key configuration file that
is being imported

Note: I may have chosen the wrong "component" for this bug but i can't find an
option for the System Settings app

STEPS TO REPRODUCE
1. Open System Settings -> Shortcuts
2. Attempt to define a binding to the "Shutdown" or "Power Off" action with the
shortcut cntrl+pause

OBSERVED RESULT
Once the control key is pressed, the UI ignores the pause key, so the action
ends up bound to the control key alone

EXPECTED RESULT
Bind cntrl+pause to power off

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.2
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-17-generic (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 500151] Writes runtime configuration to /usr/share

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

TraceyC  changed:

   What|Removed |Added

 CC||kde...@tlcnet.info

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

[plasma-systemmonitor] [Bug 500523] New: System Monitor crash when trying to edit Overview page

2025-02-21 Thread Jeff

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

Bug ID: 500523
   Summary: System Monitor crash when trying to edit Overview page
Classification: Applications
   Product: plasma-systemmonitor
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: jeffrichard...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Application: plasma-systemmonitor (5.27.5)

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

-- Information about the crash:
On the Overview page click edit page then click on one of the top four squares
like you're trying to add sensor data to it. It will immediately crash when you
click one of the squares. I just checked and it seems trying to edit any space
on the overview page will crash system monitor as soon as you click on the
space. It happens every time.

The crash can be reproduced every time.

-- Backtrace:
Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault

   PID: 30723 (plasma-systemmo)
   UID: 1000 (jeff)
   GID: 1000 (jeff)
Signal: 11 (SEGV)
 Timestamp: Fri 2025-02-21 08:33:49 CST (1min 7s ago)
  Command Line: /usr/bin/plasma-systemmonitor
Executable: /usr/bin/plasma-systemmonitor
 Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fplasma\x2dsystemmonitor-4b7bf22f77e54fa69c6dfd8b332096c1.scope
  Unit: user@1000.service
 User Unit:
app-\x2fusr\x2fbin\x2fplasma\x2dsystemmonitor-4b7bf22f77e54fa69c6dfd8b332096c1.scope
 Slice: user-1000.slice
 Owner UID: 1000 (jeff)
   Boot ID: aff94c9c4d79442d90537067196ddb85
Machine ID: cdbc50642ff24e35abd3591f4a7b97d8
  Hostname: debian
   Storage:
/var/lib/systemd/coredump/core.plasma-systemmo.1000.aff94c9c4d79442d90537067196ddb85.30723.174014842900.zst
(present)
  Size on Disk: 14.1M
   Message: Process 30723 (plasma-systemmo) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.33-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.33-1~deb12u1.amd64
Stack trace of thread 30723:
#0  0x7f5416ca9ebc n/a (libc.so.6 + 0x8aebc)
#1  0x7f5416c5afb2 raise (libc.so.6 + 0x3bfb2)
#2  0x7f541643183d _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x583d)
#3  0x7f5416c5b050 n/a (libc.so.6 + 0x3c050)
#4  0x7f54184746c4 _ZNK12KConfigGroup6configEv
(libKF5ConfigCore.so.5 + 0x2c6c4)
#5  0x7f541847b3e2
_ZNK12KConfigGroup9readEntryEPKcRK8QVariant (libKF5ConfigCore.so.5 + 0x333e2)
#6  0x7f541852663a
_ZNK12KConfigGroup9readEntryIbEET_PKcRKS1_ (libKF5Service.so.5 + 0x1f63a)
#7  0x7f54080429ca
_ZN9KSysGuard20SensorFaceController15sensorsConfigUiEv
(libKSysGuardSensorFaces.so.1 + 0x149ca)
#8  0x7f540804a26b n/a (libKSysGuardSensorFaces.so.1 +
0x1c26b)
#9  0x7f540804a5f3
_ZN9KSysGuard20SensorFaceController11qt_metacallEN11QMetaObject4CallEiPPv
(libKSysGuardSensorFaces.so.1 + 0x1c5f3)
#10 0x7f54187a0219 n/a (libQt5Qml.so.5 + 0x1a0219)
#11 0x7f54187a15f3
_ZN3QV414QObjectWrapper26virtualResolveLookupGetterEPKNS_6ObjectEPNS_15ExecutionEngineEPNS_6LookupE
(libQt5Qml.so.5 + 0x1a15f3)
#12 0x7f54187c0b96 n/a (libQt5Qml.so.5 + 0x1c0b96)
#13 0x7f54187c53df n/a (libQt5Qml.so.5 + 0x1c53df)
#14 0x7f5418757c2e
_ZN3QV48Function4callEPKNS_5ValueES3_iPKNS_16ExecutionContextE (libQt5Qml.so.5
+ 0x157c2e)
#15 0x7f54188e144d
_ZN24QQmlJavaScriptExpression8evaluateEPN3QV48CallDataEPb (libQt5Qml.so.5 +
0x2e144d)
#16 0x7f54188e7604 _ZN11QQmlBinding8evaluateEPb
(libQt5Qml.so.5 + 0x2e7604)
#17 0x7f54188eb813 n/a (libQt5Qml.so.5 + 0x2eb813)
#18 0x7f54188e9354
_ZN11QQmlBinding6updateE6QFlagsIN16QQmlPropertyData9WriteFlagEE (libQt5Qml.so.5
+ 0x2e9354)
#19 0x7f54188f6872
_ZN17QQmlObjectCreator8finalizeER26QQmlInstantiationInterrupt (libQt5Qml.so.5 +
0x2f6872)
#20 0x7f5418886b2c
_ZN20QQmlComponentPrivate8completeEP17QQmlEnginePrivatePNS_17ConstructionStateE
(libQt5Qml.so.5 + 0x286b2c)
#21 0x7f54188890a1
_ZN20QQmlComponentPrivate14completeCreateEv (libQt5Qml.so.5 + 0x2890a1)
#22 0x7f541888a7d0
_ZN13QQmlComponent12createObjectEP14QQmlV4Function (libQt5Qml.so.5 + 0x28a7d0)

[Skanpage] [Bug 500524] New: Skanpage is too noisy when files are added to or deleted from the default save location

2025-02-21 Thread Sergio

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

Bug ID: 500524
   Summary: Skanpage is too noisy when files are added to or
deleted from the default save location
Classification: Applications
   Product: Skanpage
   Version: 24.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: a.stipp...@gmx.net
  Reporter: sergio.calleg...@gmail.com
  Target Milestone: ---

SUMMARY

It appears that skanpage *watches* the default save location directory. If
files are added to it or deleted from it externally from skanpage, then
skanpage becomes too noisy on the terminal, with repeated messages such as:

```
kf.kio.widgets.kdirmodel: No node found for item that was just removed:
QUrl("file:///home/me/tmp/Scanner/250128.pdf")
```

STEPS TO REPRODUCE
1. Open skanpage from the terminal
2. Externally add/remove files from the default save dir

OBSERVED RESULT

One or two complaints are made on the terminal for each touched file

EXPECTED RESULT

Skanpage should not complain for an activity that is rather normal

SOFTWARE/OS VERSIONS

Operating System: Manjaro Linux 
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.12.12-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4750HQ CPU @ 2.00GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Pro Graphics P5200
Manufacturer: Notebook
Product Name: W740SU

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 500438] klipper popup-menu closes directly after clicking on 'invoke action'

2025-02-21 Thread cwo

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

cwo  changed:

   What|Removed |Added

 CC||cwo@posteo.net
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #5 from cwo  ---
I can confirm this. It works if you use it in the panel, but it doesn't work in
the Meta+V popup.

(the experience isn't exactly great in the panel popup version either, but at
least it works)

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

[konsole] [Bug 500515] New: [export/html] html output has random glyph, not looking like what I have in Konsole

2025-02-21 Thread David REVOY

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

Bug ID: 500515
   Summary: [export/html] html output has random glyph, not
looking like what I have in Konsole
Classification: Applications
   Product: konsole
   Version: 22.12.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Hi,

I love exporting terminal output of konsole as html but the result is always
broken as soon as a special character is part of the output.

## How to reproduce

1. Open Konsole
2. Write command lines that output special characters (eg. 'tree' is good for
that)
3. Export the output as HTML (File → Save Output As and select an html file
format).
4. Host your HTML file, and open it in Firefox.

## Result: 

The special characters are corrupted, and random glyph appears. Example:
https://peppercarrot.com/extras/forum/2025-02-21_konsole-default-html-output.html
( screenshot:
https://peppercarrot.com/extras/forum/2025-02-21_screenshot_122028_net.jpg )

## Expectation

It should looks like what I had in konsole, like that:
https://peppercarrot.com/extras/forum/2025-02-21_screenshot_123118_net.jpg

## Workaround

I saw the html output file don't have any header, or set any charsets.  If one
manually edit the html output file with Kate, and insert at the start of the
file:
```





```

Then the output will be readable again. Here is an example: 
https://peppercarrot.com/extras/forum/2025-02-21_konsole-default-html-output_FIXED.html

Too bad this workaround is tedious to do over and over again, I would
appreciate an automatic way to get this (or another fix) to read and transmit
my HTML output correctly. Thank you.

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

[plasmashell] [Bug 499298] Simplify Clock's right-click related options

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||6.4.0
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/-/commi
   ||t/cb4085d0a0ff0222d11b40446
   ||8fd11b77e709899
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Nate Graham  ---
Git commit cb4085d0a0ff0222d11b404468fd11b77e709899 by Nate Graham.
Committed on 21/02/2025 at 14:45.
Pushed by ngraham into branch 'master'.

applets/digitalclock: reduce number of context menu configure actions

Right now there are three:

- Adjust Date and Time…
- Set Time Format…
- Configure Digital Clock…

They're all very similar, and to some people might even sound the same.
Hard to figure out what specifically they refer to, reducing the ability
to quickly parse the menu.

In addition, the first two aren't even needed: links to these KCMs are
present via buttons on the config window you access with the third one.

Accordingly, remove the first two items.
FIXED-IN: 6.4.0

M  +0-12   applets/digital-clock/package/contents/ui/main.qml

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

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

[plasmashell] [Bug 497204] Plasmashell crashes in qDeleteAll on monitor wake

2025-02-21 Thread gvgeo

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

gvgeo  changed:

   What|Removed |Added

 CC||ja...@okonski.org

--- Comment #32 from gvgeo  ---
*** Bug 499266 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 499266] Taskbar disappears after idle/display outputs change

2025-02-21 Thread gvgeo

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

gvgeo  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from gvgeo  ---
(In reply to Haakon Nilsen from comment #5)
> It looks like several of the comments on #497204 (including mine) describe
> this same problem.
> 
> I'm definitely seeing the same thing on Plasma 6.3, also with HDMI, although
> with an Intel GPU.

Indeed #497204 is very similar and probably same cause. 

I did check again. And although X11 does not appear to crash the panel(maybe it
does, but recovers it too fast) when turning off the display,  soon turns on
again as it does in wayland.
And has the same 2 errors in log without crashing:
kde.plasmashell: requesting unexisting screen available rect -1
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.

Marking as duplicate, for now. If more differentiated info comes up, can
reopen.

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

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

[kwin] [Bug 499913] kwin_wayland uses 100% CPU when I drag window to top edge multiple times and freezes desktop

2025-02-21 Thread antonio

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

--- Comment #20 from antonio  ---
Waiting for the bug to be fixed, I attached a temporary patch to avoid the
desktop freeze, exiting the loop after a few seconds, I recompiled the source
for debian and verified: even if the bug is not solved, in case of freeze the
desktop now unlocks after 5 seconds.
I confirm however that the problem is in src/windows.cpp in the lines with the
"for(;;)" loops.

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

[kwin] [Bug 499846] kwin is crashing whenever I plug/unplug HDMI external LCD

2025-02-21 Thread Brian

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

--- Comment #7 from Brian  ---
Thank you for fixing this bug. I really appreciate you! <3 <3

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

[Spectacle] [Bug 500545] New: Spectacle could show a "closed hand" cursor when a Rectangle Region is being dragged

2025-02-21 Thread Eamonn Rea

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

Bug ID: 500545
   Summary: Spectacle could show a "closed hand" cursor when a
Rectangle Region is being dragged
Classification: Applications
   Product: Spectacle
   Version: 24.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: eamonn...@protonmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
Spectacle shows a hand cursor when over a draggable Rectangle Region. As a
minor UI tweak, it could change to show the "closed hand" cursor when said
region is being dragged.

I am not sure if this is documented in or goes against any KDE Human Interface
Guidelines, it was just behaviour I observed from other applications and
noticed that Spectacle does not do this.

STEPS TO REPRODUCE
1. Create a Rectangle Region when taking a screenshot/screencast.
2. Drag this region.
3. The cursor does not change when the region is being dragged.

OBSERVED RESULT
Spectacle shows an "open hand" cursor when a Rectangle Region is being dragged.

EXPECTED RESULT
Spectacle could show a "closed hand" cursor while a Rectangle Region is being
dragged.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Graphics Platform: Wayland

ADDITIONAL INFORMATION

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

[kwin] [Bug 452117] kwin on wayland: mouse pointer is synchronized or not using hardware cursor.

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

Joao Bueno  changed:

   What|Removed |Added

 Blocks||500544


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=500544
[Bug 500544] kwin on wayland: mouse pointer is synchronized or not using
hardware cursor.
-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 500544] kwin on wayland: mouse pointer is synchronized or not using hardware cursor.

2025-02-21 Thread Bug Janitor Service

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

--- Comment #1 from Bug Janitor Service  ---

Thank you for the bug report!

Please note that Plasma 6.2.5 will not be supported for much longer by KDE;
supported versions are 5.27., and 6.3 or newer.

Please upgrade to the latest version as soon as your distribution makes it
available to you. Plasma is a fast-moving project, and bugs in one version are
often fixed in the next one.

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

[Akonadi] [Bug 455787] KOrganizer DAV Groupware manual selection crashes

2025-02-21 Thread Bug Janitor Service

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

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #4 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/pim/kdepim-runtime/-/merge_requests/196

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

[kwin] [Bug 500544] kwin on wayland: mouse pointer is synchronized or not using hardware cursor.

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

--- Comment #2 from Joao Bueno  ---
Wait -

looks like it is a hardware issue on my USB-C -> USB-A adapter  (and therefore
multiple mouses misbehaving,
in the same week I changed computers for one with a newer system and Plasma
6.2)

I will wait until the end of the day before closing, though - it is some quite
erratic behavior-
(in other news, just now I perceived the "cloned" bug was cloned as "fixed"
despite re-asking
questions)

I apologise for the noise.

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

[frameworks-solid] [Bug 412851] Mounting external encrypted LUKS partition ignores keyfile

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

xusmv...@anonaddy.me changed:

   What|Removed |Added

 CC||xusmv...@anonaddy.me

--- Comment #1 from xusmv...@anonaddy.me ---
I've got the exact same problem. I wonder if there is no interest in this by
now?

Kubuntu 24.04
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1

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

[plasmashell] [Bug 500547] New: Does not enable Bluetooth audio output when speaker is muted

2025-02-21 Thread Henning

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

Bug ID: 500547
   Summary: Does not enable Bluetooth audio output when speaker is
muted
Classification: Plasma
   Product: plasmashell
   Version: 6.3.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Bluetooth in general
  Assignee: plasma-b...@kde.org
  Reporter: boredsquir...@secure.mailbox.org
  Target Milestone: 1.0

I need to check if this is reproducible.

I had my main speaker muted, and connected my bluetooth headphones. They were
displayed as a headset and connected, but the popup when switching audio
devices did not appear.

Also, the device was not shown as an option for the audio sink device.

When disconnecting the headset, unmuting the speakers, and connecting it again,
it was displayed as a headset and shown as a device.

But it was not shown as a dropdown option but a parallel device, this may be
something weird with pipewire.

I am using EasyEffects Flatpak in the background but never had issues with
that.

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.12.15-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Xe Graphics

pipewire-libs-1.2.7-1.fc41.x86_64
pipewire-pulseaudio-1.2.7-1.fc41.x86_64
pipewire-jack-audio-connection-kit-libs-1.2.7-1.fc41.x86_64
pipewire-alsa-1.2.7-1.fc41.x86_64
pipewire-1.2.7-1.fc41.x86_64
kpipewire-6.3.0-1.fc41.x86_64
pipewire-plugin-libcamera-1.2.7-1.fc41.x86_64
pipewire-gstreamer-1.2.7-1.fc41.x86_64
pipewire-utils-1.2.7-1.fc41.x86_64
pipewire-jack-audio-connection-kit-1.2.7-1.fc41.x86_64

bluez-libs-5.79-1.fc41.x86_64
bluez-5.79-1.fc41.x86_64
bluez-obexd-5.79-1.fc41.x86_64
kf6-bluez-qt-6.11.0-1.fc41.x86_64
bluez-cups-5.79-1.fc41.x86_64
NetworkManager-bluetooth-1.50.2-1.fc41.x86_64
bluedevil-6.3.0-1.fc41.x86_64

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

[plasmashell] [Bug 499420] Plasma switches to software rendering backend after waking from screen lock

2025-02-21 Thread Byron

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

Byron  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from Byron  ---
(In reply to John Kizer from comment #2)
> Hi - for what it's worth, I don't see this issue on my Fedora KDE 41 device
> with an NVIDIA card and proprietary drivers.
> 
> Just to check - do you have multiple monitors? If so, does the issue also
> occur if only one monitor is attached?
> 
> And does the issue occur if only the monitors power down, or does it happen
> when the overall device also enters a sleep state?
> 
> Thanks!

I'm not entirely sure what changed but I haven't noticed this issue anymore, so
I think I'll just call this resolved.

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

[kwin] [Bug 500544] New: kwin on wayland: mouse pointer is synchronized or not using hardware cursor.

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

Bug ID: 500544
   Summary: kwin on wayland: mouse pointer is synchronized or not
using hardware cursor.
Classification: Plasma
   Product: kwin
   Version: 6.2.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: gwid...@gmail.com
CC: felixonm...@archlinux.org, gwid...@gmail.com,
johan.claudebreunin...@gmail.com, kokok...@gmail.com,
kwin-bugs-n...@kde.org, n...@kde.org,
xaver.h...@gmail.com
Depends on: 452117
  Target Milestone: ---
 Flags: nouveau+

+++ This bug was initially created as a clone of Bug #452117 +++

(new reporter here - I got the exact same behavior as the O.P.  on bug 452117 

touchpad moves the pointer smoothly around, wireless mouse will behave exactly
as
described bellow, to the point of disrupting workflow)


SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
SUMMARY
***
There is cursor input lag
***


STEPS TO REPRODUCE
1. In the compositor settings, switch from lowest latency to higher one
2. see that mouse lag changes

You can even try to saturate the gpu use; the mouse will start to stutter too.
Under Xorg, i've regular hardware mouse cursor.



OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=452117
[Bug 452117] kwin on wayland: mouse pointer is synchronized or not using
hardware cursor.
-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 500540] downloads from wehbiste don't work

2025-02-21 Thread Israel Carazo

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

Israel Carazo  changed:

   What|Removed |Added

  Component|general |general
Product|www.kde.org |kdevelop
   Assignee|kde-...@kde.org |kdevelop-bugs-n...@kde.org

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

[konsole] [Bug 500364] bold font

2025-02-21 Thread Filip

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

--- Comment #10 from Filip  ---
Sorry, I don't know

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

[digikam] [Bug 500525] avif metatags

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 CC||metzping...@gmail.com
   Version Fixed In||8.6.0
 Status|REPORTED|RESOLVED

--- Comment #1 from Maik Qualmann  ---
To write metadata to AVIF files, writing with ExifTool must be activated in the
digiKam settings under Metadata. Only ExifTool can write to AVIF files.

Maik

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

[digikam] [Bug 500525] Writing metadata to AVIF files.

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

Maik Qualmann  changed:

   What|Removed |Added

Summary|avif metatags   |Writing metadata to AVIF
   ||files.

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

[frameworks-kconfig] [Bug 498473] Provide a mechanism to return the keys in a group via the KWrite- and KReadConfig binaries.

2025-02-21 Thread Ben Erickson

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

Ben Erickson  changed:

   What|Removed |Added

 CC||bnerickso...@gmail.com

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

[kde] [Bug 500548] New: Mounting a LUKS encrypted device via GUI ignores keyfile defined in crypttab.

2025-02-21 Thread boernsen

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

Bug ID: 500548
Summary: Mounting a LUKS encrypted device via GUI ignores
keyfile defined in crypttab.
Classification: I don't know
Product: kde
Version: unspecified
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: xusmv...@anonaddy.me
Target Milestone: ---

Mounting a LUKS encrypted device via GUI always shows password prompt despite
keyfile definition in crypttab.

Possible duplicate of https://bugs.kde.org/show_bug.cgi?id=412851
It's a different platform though and I though I should give more description.

STEPS TO REPRODUCE
1. Encrypt USB device with cryptsetup and add a keyfile to it
2. Add entry for device with keyfile in /etc/crypttab
3. Try to mount the device with cryptdisks_start / mount via terminal, then
umount / cryptdisks_stop.
4. Try to mount the device via GUI (either via KDE dolphin or via task bar
"Disks & Devices").

OBSERVED RESULT
Mounting via cryptdisks_start works without password prompt due to keyfile in
crypttab.
Mounting via GUI shows password prompt, thus doesn't respect the keyfile
defined in crypttab.

EXPECTED RESULT
Mounting via GUI uses keyfile defined in crypttab and omits the password prompt
in that case.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 24.04
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1

ADDITIONAL INFORMATION
https://askubuntu.com/questions/1541875/how-to-unmount-an-encrypted-usb-via-gui-using-a-keyfile

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

[plasmashell] [Bug 500549] New: Hovering over an extra in popup makes it blurry

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

Bug ID: 500549
   Summary: Hovering over an extra in popup makes it blurry
Classification: Plasma
   Product: plasmashell
   Version: 6.3.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Clipboard widget & pop-up
  Assignee: plasma-b...@kde.org
  Reporter: nilskemail+...@gmail.com
  Target Milestone: 1.0

Created attachment 178707
  --> https://bugs.kde.org/attachment.cgi?id=178707&action=edit
Screenshot of the popup with a blurry looking text item

SUMMARY
Hovering over a text item in the clipboard pop-up makes it look blurry

STEPS TO REPRODUCE
1. Copy some text
2. Open the clipboard popup (either by clicking on the icon in the taskbar, or
pressing Meta+V)
3. Hover with you mouse over a text item

OBSERVED RESULT
The text item looks blurry

EXPECTED RESULT
The text item should still look as sharp as the others

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.12.13-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon  780M Graphics
Memory: 30.6 GiB of RAM
Graphics Processor: AMD Radeon 780M

ADDITIONAL INFORMATION
I am using 125% display scaling, maybe that has an impact

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

[okular] [Bug 499547] Unable to scroll when using auto fit after coming from a bigger zoom level

2025-02-21 Thread Davide Maria Giambirtone

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

--- Comment #3 from Davide Maria Giambirtone  
---
Created attachment 178708
  --> https://bugs.kde.org/attachment.cgi?id=178708&action=edit
Okular showing broken behaviour on linux

Hi, so sorry to come back to you so late, it's the first bug report i create
here and i'm used to them beng on github

Anyhow, i think i may have written the wrong stuff, this bug happens when
zooming to >100% and then using Auto Fit, not Fit Page
I'll show a recorded video from my phone (sorry for the quality) of it
happening on linux, it's the same on windows tho, and it happends even for the
most basic files

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

[okular] [Bug 499547] Unable to scroll when using auto fit after coming from a bigger zoom level

2025-02-21 Thread Davide Maria Giambirtone

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

--- Comment #4 from Davide Maria Giambirtone  
---
(In reply to Davide Maria Giambirtone from comment #3)
> Created attachment 178708 [details]
> Okular showing broken behaviour on linux
> 
> Hi, so sorry to come back to you so late, it's the first bug report i create
> here and i'm used to them beng on github
> 
> Anyhow, i think i may have written the wrong stuff, this bug happens when
> zooming to >100% and then using Auto Fit, not Fit Page
> I'll show a recorded video from my phone (sorry for the quality) of it
> happening on linux, it's the same on windows tho, and it happends even for
> the most basic files

i also added in t he video the fact that, when in that locked state, zooming
will allow you to then scroll the pages
Also i'm on version 24.12.2, i don't think it has changed since i submitted
this bug report

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

[dolphin] [Bug 500265] half screen view hides location bar initially

2025-02-21 Thread israel

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

--- Comment #7 from israel  ---
Created attachment 178699
  --> https://bugs.kde.org/attachment.cgi?id=178699&action=edit
hTVT37is0N1l07Ss.png

--- Comment #8 from israel  ---
Created attachment 178700
  --> https://bugs.kde.org/attachment.cgi?id=178700&action=edit
56nuRHznLdkL0Ezx.png

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

[dolphin] [Bug 500315] Changing file/folder permissions as root doesn't work

2025-02-21 Thread Damglador

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

Damglador  changed:

   What|Removed |Added

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

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

[dolphin] [Bug 498981] Don't open a new tab for "Open as Administrator" or close it after use

2025-02-21 Thread Damglador

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

--- Comment #1 from Damglador  ---
This is also an inconsistent behavior. The other way to work as administrator
in Dolphin is a banner that pops up sometimes above the file views, it happens
is admin permissions run out, or if you enter some folders (for me, it's /root,
which has set "No access" for "Others" in permissions). If you use the "Work as
admin" button on the banner, it will actually just escalate permissions of the
current tab to root, without opening an additional tab.

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

[digikam] [Bug 500525] Writing metadata to AVIF files.

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

--- Comment #3 from Maik Qualmann  ---
I have now tested it again and it works 100%. Which ExifTool version are you
using? Otherwise, please provide a sample AVIF image with which the problem can
be reproduced, if not public, then to my private email.

Maik

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

[kasts] [Bug 500431] F-droid - hash error

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

b...@mogwai.be changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #9 from b...@mogwai.be ---
Glad that the issue is solved?

I don't think there is another version in the fdroid repo. There might be one
in another repo, or maybe fdroid simply has a bug triggered by repo preference.
In any case, it seems to be clear that the actual package download does work.

I'll close this issue now. Thanks for reporting anyway. It's better to know
about potential issues, even if they turn out to be out of our hands in the
end.

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

[kdiff3] [Bug 486401] Lagging/Slow scrolling

2025-02-21 Thread michael

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

--- Comment #9 from michael  ---
Thanks. I use arch myself but kiff3 installed from the current stable branch in
Debug configuration. Originally I did see it in 1.11.x.

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

[plasma-integration] [Bug 500546] SVG for icons in plasma

2025-02-21 Thread Simona Pisano

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

--- Comment #2 from Simona Pisano  ---
Created attachment 178706
  --> https://bugs.kde.org/attachment.cgi?id=178706&action=edit
image 3

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

[digikam] [Bug 500525] Writing metadata to AVIF files.

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

--- Comment #6 from Maik Qualmann  ---
ExifTool 12.76 is quite old. In version 13.11 a bug was fixed for writing Exif
metadata.
Test our AppImage to make sure it works, it contains a current ExifTool
version.

Maik

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

[kpat] [Bug 500334] kPatience game is not opening on Ubuntu

2025-02-21 Thread fern

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

--- Comment #4 from fern  ---
I got it from Ubuntu 24.04.2 LTS /App Center Version 1.0.0 being referred for
kPatience Channel latest/edge 24.12.0, License GPL-2.0+, Version 24.12.0,
Published Dec 30,2024

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

[neon] [Bug 500533] New: No hardware brightness controls by default for external monitor

2025-02-21 Thread Jakob Petsovits

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

Bug ID: 500533
   Summary: No hardware brightness controls by default for
external monitor
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages Testing Edition
  Assignee: neon-b...@kde.org
  Reporter: jpe...@petsovits.com
CC: j...@jriddell.org, neon-b...@kde.org
  Target Milestone: ---

SUMMARY
Updated to KDE neon (Testing) shortly after the Plasma 6.3.1 release, and
noticed that my monitor's DDC/CI hardware brightness settings are inaccessible.

Plasma will still provide software brightness instead, but this can only dim
the screen, it won't be able to raise my brightness from 30 to 70 on the
monitor itself. Furthermore, software dimming will necessarily reduce the
available color gamut because if you cap the maximum pixel color value, you
have fewer colors available overall.

Installing the `ddcutil` package will fix this. Strictly speaking it should
already work with the (preinstalled by default) libddcutil library /
`libddcutil4` package, however the udev rules that provide the required
permissions are part of the `ddcutil` package so libddcutil by itself is
neutered on Debian-based systems.

STEPS TO REPRODUCE
1. Connect external monitor
2. Log into Plasma session
3. Click "Brightness and Color" applet icon in the system tray

OBSERVED RESULT
There is a brightness slider for your external monitor, but it's separate from
the monitor's OSD menu. It will start out at 100% and can only dim the monitor.

EXPECTED RESULT
There is a brightness slider for your external monitor, and after moving the
slider, the monitor's built-in OSD menu will show the same percentage as what
you configured using the applet.

SOFTWARE/OS VERSIONS
Operating System: Ubuntu 24.04.2 LTS (Noble Numbat)
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-17-generic (64-bit)
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

ADDITIONAL INFORMATION
Installing the `ddcutil` package (to fix this) will additionally draw in the
package dependencies `i2c-tools`, `libi2c0` and `read-edid`.

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

[Discover] [Bug 500539] New: Stray update fields on Tasks modal window

2025-02-21 Thread Emir SARI

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

Bug ID: 500539
   Summary: Stray update fields on Tasks modal window
Classification: Applications
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: emir_s...@icloud.com
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 178701
  --> https://bugs.kde.org/attachment.cgi?id=178701&action=edit
screenshot

Latest Kinoite, tr_TR locale.

I am not sure how to reproduce this. When I was performing updates, the system
one to be exact, the Tasks modal dialogue suddenly started displaying these
empty rows. Maybe something can be done to ensure it doesn’t go awry.

See screenshot.

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

[yakuake] [Bug 500538] New: Yakuake on X11 flickers over the top panel

2025-02-21 Thread Siddhartha

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

Bug ID: 500538
   Summary: Yakuake on X11 flickers over the top panel
Classification: Applications
   Product: yakuake
   Version: 24.12.2
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: k...@sdht.in
  Target Milestone: ---

When invoking the Yakuake with a panel positioned at the top of the screen,
yakuake flickers in the part covering the panel. It seems like the rendering of
Yakuake and the panel is conflicting.

Things that help: moving the panel to the bottom (yakuake doesn't overlap
anymore) or changing the panel to "autohide"/"windows go below".

X11+QEMU virgl on a macOS might be highly relevant here.

SOFTWARE/OS VERSIONS
Operating System: NixOS 25.05 (unstable)
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3 (64-bit)
Graphics Platform: X11
Processors: 12
Memory: 47.7 GiB of RAM
Graphics Processor: virgl
Manufacturer: QEMU
Product Name: QEMU Virtual Machine
System Version: virt-9.1

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

[kwin] [Bug 500511] Right-clicking on a scrollbar in Kwin debug console locks all input

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

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

[plasmashell] [Bug 500442] Child menus do not appear instantly when cursor is rapidly moved up and down

2025-02-21 Thread Ned

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

--- Comment #11 from Ned  ---
Removing the panel seems to help(?)... I'll see how things improve after panel
recreation.

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

[KScreen] [Bug 500531] Can't select appropriate scale setting in Display Settings

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

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

[kwin] [Bug 500519] KWin crashes when bogus size window is created

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

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

[kwin] [Bug 476047] Ctrl+Meta+scroll zooms in a mostly unusable way when scrolling with a touchpad

2025-02-21 Thread Duncan

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

--- Comment #5 from Duncan <1i5t5.dun...@cox.net> ---
(In reply to TraceyC from comment #4)
> I tested ths with a Firefox window on two different systems with trackpads -
> 6.3.0 and git-master
> I was using Ctrl+two finger pinch
> I can confirm that on both systems, the zoom is overly sensitive.

FWIW what you're testing with ctrl-pinch in firefox is /not/ kwin/plasma's zoom
mechanism for the entire desktop (including non-firefox windows), but firefox's
own independent zoom mechanism (that will only zoom firefox, not non-firefox
windows).  That would therefore be firefox's bug and need filed with them, not
kwin/kde's.

The bug here is for the kwin full-desktop (and all apps including firefox) zoom
mechanism, accessed with ctrl-meta (aka ctrl-win) two-finger-scroll
(hard-coded, plus any hotkey configured at the location in comment #1 footnote
#1).

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

[dolphin] [Bug 500066] Dolphin freezes when trying to open right click context menu on HDD while having selected many files

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

--- Comment #4 from TraceyC  ---
Thanks for the flamegraph!

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

[kwin] [Bug 476047] Ctrl+Meta+scroll zooms in a mostly unusable way when scrolling with a touchpad

2025-02-21 Thread Bernhard

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

--- Comment #6 from Bernhard  ---
Since this issue seems to have picked up activity now I've tried again now
(different, newer laptop - not sure it matters).

Apparently the behaviour has changed, now both scrolling directions seem to get
"rounded up" to a full scroll event. The only saving grace that makes it at all
usable with lower zoom factors is that, while the "zoom animation" is going on,
it ignores further scroll events.

This leads to the awkward behavior where the amount you zoom doesn't depend on
on distance-scrolled, but the time-scrolled.

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

[plasma-systemmonitor] [Bug 500534] New: System Monitor sometimes crashes when moving in the process tab

2025-02-21 Thread NovaliX

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

Bug ID: 500534
   Summary: System Monitor sometimes crashes when moving in the
process tab
Classification: Applications
   Product: plasma-systemmonitor
   Version: git-stable-Plasma/6.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: nova...@protonmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 178693
  --> https://bugs.kde.org/attachment.cgi?id=178693&action=edit
The backtrace of system monitor. Done using gdb and debuginfod.

SUMMARY
Sometimes, when moving into the process tab, the application crashes. 

STEPS TO REPRODUCE
1. Open System monitor and go into the process tab
2. Try to move around into the process tab.
3. If it works as expected, relaunch System monitor and try again.

OBSERVED RESULT
The applications crashes

EXPECTED RESULT
We should be able to move around the process tab

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

ADDITIONAL INFORMATION
Below is the backtrace informations.

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

[kdiff3] [Bug 486401] Lagging/Slow scrolling

2025-02-21 Thread Andrej M.

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

--- Comment #6 from Andrej M.  ---
Hi,

thank you for your patch, but for me it didn't seem to work. I used the trixie
package (1.12.0) as base (https://packages.debian.org/trixie/kdiff3), applied
the patch and rebuild. No change to laggines in both virtualbox and live
system. I used HTML source of https://kde.org in two different languages. I'm
however a newbie when it comes to building packages, so it would be great if
other commenters could also test this.

Best regards,
Andrej

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

[Haruna] [Bug 500327] Neither the 'i' or 'SHIFT+i' shortcuts work in Haruna to show the statistics and also cannot be configured in the Settings -> Shortcuts

2025-02-21 Thread John

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

--- Comment #3 from John  ---
After seeing this comment here:
https://bugs.kde.org/show_bug.cgi?id=491154#c4
Now I realize that the custom command sucks even more, besides the fact that it
shows the stats just for a few seconds, there are other pages that cannot be
seen.
I guess it's one more reason to just use MPV instead of Haruna.

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

[plasmashell] [Bug 500442] Child menus do not appear instantly when cursor is rapidly moved up and down

2025-02-21 Thread Ned

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

--- Comment #9 from Ned  ---
It's gotten worse. Plasma now locks up. Config file damaged? I'm gonna try
remaking the panel.

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

[kdiff3] [Bug 486401] Lagging/Slow scrolling

2025-02-21 Thread Andrej M.

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

--- Comment #8 from Andrej M.  ---
Created attachment 178702
  --> https://bugs.kde.org/attachment.cgi?id=178702&action=edit
Callgrind profile

I'm attaching the callgrind profile which was created with invoking: valgrind
--tool=callgrind kdiff3 test1.txt test2.txt
Both files had approx 450 short lines. After the gui was opened, I dragged the
scrollbar and closed the program when it stopped scrolling.

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

[kwin] [Bug 500450] Weird resizing issues in some OpenGL apps in Plasma 6.3.0

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
   Severity|normal  |minor
   Keywords||regression

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

[systemsettings] [Bug 500469] Move technical SDDM settings into other KCMs so its current location makes more sense

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

Nate Graham  changed:

   What|Removed |Added

Summary|SDDM behaviour should not   |Move technical SDDM
   |be under "Colours & Themes" |settings into other KCMs so
   |settings|its current location makes
   ||more sense
 CC||n...@kde.org
 Status|REOPENED|CONFIRMED
   Severity|normal  |task

--- Comment #3 from Nate Graham  ---
Yeah, the intention here is to split the KCM, and keep the side that deals with
appearance where it is, and move all the technical features into the Desktop
Session and User KCMs. It's just that it hasn't happened yet.

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

[kwin] [Bug 500526] Night light not working in Wayland session

2025-02-21 Thread Zamundaaa

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

Zamundaaa  changed:

   What|Removed |Added

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

--- Comment #1 from Zamundaaa  ---
Do you have an ICC profile set on the display?

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

[digikam] [Bug 500525] Writing metadata to AVIF files.

2025-02-21 Thread Duns

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

--- Comment #5 from Duns  ---
This is my digikam config:
digiKam: 8.5.0
KDE Frameworks: 6.11.0
Qt: Using 6.8.2 and built against 6.8.2
Ubuntu 24.04.2 LTS (Xcb)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.11.0-17-generic

and exiftool is 12.76

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

[digikam] [Bug 500525] Writing metadata to AVIF files.

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

--- Comment #4 from Maik Qualmann  ---
Your configuration looks like the digiKam Snap package from Ubuntu. Snap uses a
sandbox and many problems are known with it, it is unsuitable for use with
digiKam. Use our AppImage as an alternative.

Maik

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

[kwin] [Bug 499913] kwin_wayland uses 100% CPU when I drag window to top edge multiple times and freezes desktop

2025-02-21 Thread Andrew Simmons

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

Andrew Simmons  changed:

   What|Removed |Added

 CC||agsimmo...@gmail.com

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

[kwin] [Bug 500015] On X11, Plasma freezes hard when a window is dragged to the top of the screen

2025-02-21 Thread Andrew Simmons

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

Andrew Simmons  changed:

   What|Removed |Added

 CC||agsimmo...@gmail.com

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

[plasmashell] [Bug 500505] Power icon not working

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

Nate Graham  changed:

   What|Removed |Added

Version|master  |6.3.1
 CC||n...@kde.org
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Nate Graham  ---
"Show action button captions" is on by default, FWIW. I can't reproduce this
with `LANGUAGE=ko_KO plasmashell`. With the setting on or off, the buttons
always appear as expected.

Does this issue reproduce in a new clean user account for you?

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

[kwin] [Bug 476047] Ctrl+Meta+scroll zooms in a mostly unusable way when scrolling with a touchpad

2025-02-21 Thread Bernhard

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

--- Comment #7 from Bernhard  ---
For any high precision scroll events - to my understanding - the correct
behavior should be to skip the animation entirely, and instantly zoom by the
zoom factor multiplied with the "fraction of a real scroll event" that's been
scrolled since the last event was processed (which might need to summed up if
the gpu/sw renderer is very slow and there have been more than the current one
received.) 

In any case, a smooth zoom/scroll animation just isn't compatible with high
precision scrolling exactly _because_ it doesn't stop when you do.

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

[kwin] [Bug 500535] Wayland: Translucent window artifacts remain on wallpaper after minimizing inactive windows (NVIDIA RTX 3070)

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

--- Comment #1 from 2knch...@gmail.com <2knch...@gmail.com> ---
Happens only if window is maximized.

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

[NeoChat] [Bug 499867] Neochat snap fails to start. Error: `GLIBCXX_3.4.32' not found

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

techxga...@outlook.com changed:

   What|Removed |Added

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

--- Comment #5 from techxga...@outlook.com ---
Sorry. Issue is not resolved yet

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

[kwin] [Bug 500535] New: Wayland: Translucent window artifacts remain on wallpaper after minimizing inactive windows (NVIDIA RTX 3070)

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

Bug ID: 500535
   Summary: Wayland: Translucent window artifacts remain on
wallpaper after minimizing inactive windows (NVIDIA
RTX 3070)
Classification: Plasma
   Product: kwin
   Version: 6.3.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: 2knch...@gmail.com
  Target Milestone: ---

When window translucency is enabled in KDE Plasma, minimizing an inactive
(translucent) window causes the translucent image to remain embedded in the
wallpaper until either rebooting or running 'kwin_wayland --replace &'

Environment:
- KWin version: 6.3.1
- Distribution: Arch Linux
- Session type: Wayland
- GPU: NVIDIA RTX 3070
- NVIDIA driver: 570.86.16
- CPU: Ryzen 5800H

Steps to Reproduce:
1. Enable window translucency in KDE Plasma
2. Open any window and let it become inactive (translucent)
3. Minimize the translucent window
4. Observe that the translucent window image remains stuck on the wallpaper

Current Workaround:
Running 'kwin_wayland --replace &' temporarily fixes the issue until it occurs
again.

Configuration:
~/.config/kwinrc contents:
[Compositing]
AnimationSpeed=2
Backend=XRender
GLCore=true
GLPreferBufferSwap=n
HiddenPreviews=6
OpenGLIsUnsafe=false
WindowsBlockCompositing=false

[Effect-translucency]
ComboboxPopups=81
Dialogs=80
Inactive=81
IndividualMenuConfig=true
MenuOpacity=100
MoveResize=100

[Plugins]
minimizeanimationEnabled=false
translucencyEnabled=true

Additional Notes:
- Issue persists regardless of compositor backend (OpenGL/XRender)
- Issue persists with different translucency settings
- Issue persists with minimize animations disabled

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

[kwin] [Bug 500535] Wayland: Translucent window artifacts remain on wallpaper after minimizing inactive windows (NVIDIA RTX 3070)

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

2knch...@gmail.com <2knch...@gmail.com> changed:

   What|Removed |Added

 CC||2knch...@gmail.com

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

[www.kde.org] [Bug 500540] New: downloads from wehbiste don't work

2025-02-21 Thread Israel Carazo

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

Bug ID: 500540
   Summary: downloads from wehbiste don't work
Classification: Websites
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: icara...@gmail.com
  Target Milestone: ---

When I'm trying to download the version of KDevelop for Windows or MacOs. The
link is down.

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

[kdenlive] [Bug 500542] New: Image sequence (Filename pattern) not working

2025-02-21 Thread Timwi

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

Bug ID: 500542
   Summary: Image sequence (Filename pattern) not working
Classification: Applications
   Product: kdenlive
   Version: 24.12.2
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Project Bin & Import
  Assignee: j...@kdenlive.org
  Reporter: bugs.kde@timwi.de
  Target Milestone: ---

SUMMARY

The “Add Image Sequence” command, when using the Filename pattern option, does
not find any files.

STEPS TO REPRODUCE
1. Create ≥ 11 images named “Image0.png”, “Image1.png”, etc., up to
“Image10.png” (and optionally beyond).
2. Project → Add Image Sequence, method: Filename pattern
3. Select Image0.png as the “First frame”

OBSERVED RESULT

“No image found”

EXPECTED RESULT

Images found.

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

[plasmashell] [Bug 500442] Child menus do not appear instantly when cursor is rapidly moved up and down

2025-02-21 Thread Ned

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

--- Comment #13 from Ned  ---
Switched to X11, disabled my integrated display, switched to the external one
and black screen. I am now confident now that something somewhere is damagedon
my system.

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

[kwin] [Bug 452117] kwin on wayland: mouse pointer is synchronized or not using hardware cursor.

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

Joao Bueno  changed:

   What|Removed |Added

 CC||gwid...@gmail.com

--- Comment #10 from Joao Bueno  ---
It is 2025 - Plasma 6.2 on a Fedora 41 fresh install  -- this is still an
issue, I had to workaround with the environment variable listed above.

Touchpad works smootly, but the wireless mouse is behaving as described in the
O.P. to the point of disrupting the workflow.

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

[Spectacle] [Bug 500543] New: Spectacle shows wrong cursor when resizing screenshot / screencast region

2025-02-21 Thread Eamonn Rea

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

Bug ID: 500543
   Summary: Spectacle shows wrong cursor when resizing screenshot
/ screencast region
Classification: Applications
   Product: Spectacle
   Version: 24.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: eamonn...@protonmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
When creating a Rectangle Region in Spectacle, resizing this (and sizing it
initially) will show the wrong cursor type. It shows the "open hand" cursor,
the same it would show if hovering over something that could be dragged. While
it is true the region can be dragged, when resizing by pulling at the edges and
corners, it would be more expected to show a resizing cursor. I believe
Spectacle used to do this until fairly recently.

The nature of this bug is hard to get a screenshot of, since it occurs when
attempting *to* take a screenshot, but hopefully the description and Steps to
Reproduce suffice :-)

STEPS TO REPRODUCE
1. Create a Rectangle Region with Spectacle.
2. When sizing initially, it will show an open hand cursor instead of a
resizing cursor 
3. When resizing after, it will show the same cursor type when again it would
be more expected to show a resizing cursor.

OBSERVED RESULT
Spectacle shows a hand cursor when sizing/resizing rectangle regions for
screenshots/screencasts.

EXPECTED RESULT
Spectacle should show a resize cursor when sizing/resizing rectangle regions
for screenshots/screencasts, which from memory I think was previously the case.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Graphics Platform: Wayland

ADDITIONAL INFORMATION

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

[dolphin] [Bug 500265] half screen view hides location bar initially

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

--- Comment #5 from TraceyC  ---
Thanks for the screenshots, they clearly show the problem
I'm assuming you're using an X11 session, since Wayland is currently unable to
save window positions?

Note from the screenshots:
- Dolphin Settings - interface - Status & Location bars - "Make location
editable" is enabled
- There is a different icon set than Breeze in use, it's also not Oxygen

I re-tested with git-master and Neon Testing on X11. I was still unable to
reproduce, even with making Dolphin half screen exiting it, and re-starting it.
It was still half-screen, and showed the location bar.


What's the name of the icon theme you're using? While it may not be likely to
be the cause of the issue, I want to test with the same icon set. Thanks.

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

[dolphin] [Bug 500103] Window title wraps search query with '%27' in non-indexed locations

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

TraceyC  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #4 from TraceyC  ---
(In reply to Luke Horwell from comment #3)
> It depends where the search takes place. In my testing, the title was
> correct when searching the home folder, but the window title goes bad when
> searching from the root filesystem folder (/).

Aha. This I can reproduce on git-master. Thanks!

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

[plasma-systemmonitor] [Bug 500523] System Monitor crash when trying to edit Overview page

2025-02-21 Thread Bug Janitor Service

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|REPORTED|RESOLVED

--- Comment #1 from Bug Janitor Service  ---

Thank you for the bug report!

Debian advises users to not submit bugs upstream
(https://www.debian.org/Bugs/Reporting), and Plasma 5.27.5 is no longer
eligible for support or maintenance from KDE. It's possible that the issue
exists only in Debian at this point.

Could you report the bug to Debian using the report bug utility
(https://packages.debian.org/stable/utils/reportbug)? If necessary, the
maintainer of the package will forward the bug upstream.
Thanks for understanding!

Thanks again!

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

[neon] [Bug 500527] New: SDDM widgets are tiny on hi-res screen

2025-02-21 Thread Jakob Petsovits

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

Bug ID: 500527
   Summary: SDDM widgets are tiny on hi-res screen
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages Testing Edition
  Assignee: neon-b...@kde.org
  Reporter: jpe...@petsovits.com
CC: j...@jriddell.org, neon-b...@kde.org
  Target Milestone: ---

SUMMARY
On a Framework Laptop 13 with  KDE neon (Testing) with 2880x1920 display, the
text box and other controls on the SDDM login screen are tiny. Anyone without
eagle-eyesight will need to bend their head closer to the screen in order to
use it.

SDDM can use kwin_wayland which features automatic scale detection, but this is
not currently used. Shortly after the Plasma 6.3.1 release, neon ships with two
neon-specific configuration files [1] for SDDM, neither of which specifies the
Wayland backend.

[1]
https://invent.kde.org/neon/neon/settings/-/tree/ddd432b800743541f0488da47a21b76f5cb4bcd7/usr/lib/sddm/sddm.conf.d

If I add the following file as /etc/sddm.conf.d/10-wayland.conf (courtesy of
Arch Linux wiki), sizes look just right:

> [General]
> DisplayServer=wayland
> GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
> 
> [Wayland]
> CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts 
> --locale1 --inputmethod maliit-keyboard

Let's consider adding this as default to /usr/lib/sddm/sddm.conf.d.

STEPS TO REPRODUCE
1. Install neon
2. Boot laptop

OBSERVED RESULT
Password field uses a very small font.

EXPECTED RESULT
Password field looks similar to other text boxes after session login, which are
rightly sized by default.

SOFTWARE/OS VERSIONS
Operating System: Ubuntu 24.04.2 LTS (Noble Numbat) - damn, I would have
expected this to say KDE neon Testing
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-17-generic (64-bit)
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

ADDITIONAL INFORMATION
Maliit virtual keyboard didn't show for me despite specifying it as command
line parameter. This is also true in the session though, not sure if due to
misconfiguration or Maliit deficiencies or the fact that I have a keyboard and
touchpad available. May be related to
https://invent.kde.org/neon/neon/settings/-/merge_requests/13.

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

[KBibTeX] [Bug 500536] New: Build fails with icu-76.1

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

Bug ID: 500536
   Summary: Build fails with icu-76.1
Classification: Applications
   Product: KBibTeX
   Version: 0.10
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Compiling/packaging
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: bugs.kde.org.await...@passmail.net
  Target Milestone: ---

Created attachment 178694
  --> https://bugs.kde.org/attachment.cgi?id=178694&action=edit
KBibTex build log

SUMMARY
Kbibtex fails to build with ICU-76.1

STEPS TO REPRODUCE
1. Try to compile kbibtex using icu-76.1 as a dependency
2. Build fails


OBSERVED RESULT
Please see attached log file.

EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kwin] [Bug 500535] Wayland: Translucent window artifacts remain on wallpaper after minimizing inactive windows (NVIDIA RTX 3070)