[systemsettings] [Bug 470470] Usage of setxkbmap on Wayland resets Keyboard-Layout to US (even if it is not configured)

[Wismill]

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

Wismill  changed:

   What|Removed |Added

 CC||d...@wismill.eu

--- Comment #1 from Wismill  ---
setxkbmap and xmodmap are X11-only tools and will not work with Wayland. So
e.g. `setxkbmap -query` will most probably not gives you any meaningful
information. In a Wayland session, the only way to check reliably your keymap
in X11 is to use `xkbcomp $DISPLAY -` .

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

[Discover] [Bug 485622] New: Discover's context menu entry "update" does nothing.

[haui]

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

Bug ID: 485622
   Summary: Discover's context menu entry "update" does nothing.
Classification: Applications
   Product: Discover
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Notifier
  Assignee: plasma-b...@kde.org
  Reporter: h...@gifted-minecraft.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY

The "Updates available" icon shows in the systemtray and has 4 context menu
entries: Open Discover, Show updates, Update, Close (translated from german
locale).

Clicking any other entry does what it says. Only "Update" doesnt actually
update the system. Journalctl shows "get-updates transaction /1552_eebbdcbb
from uid 1000 finished with success after 511ms" when I click the context entry
but not always.

STEPS TO REPRODUCE
1. Install Debian stable + KDE
2. Wait for Discover Update systray notifier icon
3. Right click
4. Click Update
5. Nothing happens

OBSERVED RESULT

Nothing happens

EXPECTED RESULT

Systemupdate

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian GNU/Linux 12 (bookworm) x86_64, 6.1.0-20-amd64
(available in About System)
KDE Plasma Version: Plasma 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 427589] Wrong keyboard layout

[Wismill]

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

Wismill  changed:

   What|Removed |Added

 CC||d...@wismill.eu

--- Comment #2 from Wismill  ---
setxkbmap is a X11 tool and as such will not give you a meaningful result.

On recent versions there is indeed a warning: `WARNING: Running setxkbmap
against an Xwayland server`.

Is you issue incorrect layout for X11 apps or merely incorrect result with
`setxkbmap -query`?

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

[Oxygen] [Bug 481402] question mark icons shown in systray when oxygen icon theme

[deadite66]

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

deadite66  changed:

   What|Removed |Added

 CC||lee295...@gmail.com

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

[frameworks-kiconthemes] [Bug 484639] Fallback to Breeze ignored by KIconLoader because of wrong global initialization order

[deadite66]

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

deadite66  changed:

   What|Removed |Added

 CC||lee295...@gmail.com

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

[korganizer] [Bug 485621] New: No alarams and no updates from Google - update is stuck

[bugzilla_noreply]

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

Bug ID: 485621
   Summary: No alarams and no updates from Google - update is
stuck
Classification: Applications
   Product: korganizer
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: groupware
  Assignee: kdepim-b...@kde.org
  Reporter: bn...@yahoo.com
  Target Milestone: ---

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

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

SUMMARY


STEPS TO REPRODUCE
1. Create a calendar based on Google calendar OR use an existing one
2. After creation calendar will be updated and be sown in KOrganizer.
3. BUT -
3.1.  "Update Calendar" has no effect.
3.2.  alerts are not displayed when the time comes
3.3.  Settings->Configure KOrganizer-> General->Calendars->Restart has no
effect.

OBSERVED RESULT
See 3.


EXPECTED RESULT
All of this to work.  It did before upgrading to 6.

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

ADDITIONAL INFORMATION

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

[kwin] [Bug 485620] New: Adjust the default shortcut for Mouse Mark

[Antti Savolainen]

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

Bug ID: 485620
   Summary: Adjust the default shortcut for Mouse Mark
Classification: Plasma
   Product: kwin
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: antti.s...@gmail.com
  Target Milestone: ---

SUMMARY
Demonstrative video: https://youtu.be/Zv2HtjkSskE
I feel that the default shortcut for Mouse Mark overlaps with the default
hotkey for rectangular screenshot too much. Currently Mouse Mark is done with
Ctrl+Shift+Mouse Move while Rectangular screenshot is Ctrl+Shift+PrintScreen.
This can lead to situations where a small movement of the mouse can leave a
smidge on the screen right before trying to take a shot. In the demonstrative
video I demonstrate it with bug 485619 to exaggarate the effect, but even a
small smidge could be annoying. 
I propose that the binding should be moved to Ctrl+Shift+Mouse Click+Drag

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0

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

[kate] [Bug 466175] Feature request: ruff integration for Python

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

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

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

[kwin] [Bug 485619] New: Mouse Mark desktop effect creates an unwanted line between the point mouse was on during undo and and where it is when starting to draw

[Antti Savolainen]

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

Bug ID: 485619
   Summary: Mouse Mark desktop effect creates an unwanted line
between the point mouse was on during undo and and
where it is when starting to draw
Classification: Plasma
   Product: kwin
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: antti.s...@gmail.com
  Target Milestone: ---

SUMMARY
Demonstrative video: https://youtu.be/SHYac7Dj42E
If I use the hotkey for "Clear Last Mouse Mark", Kwin will take the point where
the mouse was at that point and make it the starting point of the next mouse
mark. This will create annoying streaks on the screen.

STEPS TO REPRODUCE
1. Enable Mouse Mark
2. Use Mouse Mark to mark something on the screen
3. Erase the mark (default Ctrl+Shift+F12)
4. Move your mouse elsewhere and make a new mark there

OBSERVED RESULT
There is a giant line from the point where the erasure was made and the start
of the new mark

EXPECTED RESULT
The mark should start where the mouse is when starting to draw

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

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

[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta

[bugzilla_noreply]

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

--- Comment #12 from crimsony...@gmail.com ---
(In reply to crimsonyote from comment #11)
> I agree, we should reverse the change. Make this feature a toggle option.

It's objectively a better to do it the way it was, rather than using a weird
non-standard system. I thought KDE was about choice? Huh. So the choice to
ALWAYS show a graphical battery icon should be added back

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

[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta

[bugzilla_noreply]

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

crimsony...@gmail.com changed:

   What|Removed |Added

 CC||crimsony...@gmail.com

--- Comment #11 from crimsony...@gmail.com ---
I agree, we should reverse the change. Make this feature a toggle option.

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

[kate] [Bug 483363] Kate has crashed after using rename (F2) context menu option

[rjx_]

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

rjx_ <7c6s4b+cc6efdty3b...@sharklasers.com> changed:

   What|Removed |Added

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

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

[kate] [Bug 483363] Kate has crashed after using rename (F2) context menu option

[rjx_]

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

--- Comment #15 from rjx_ <7c6s4b+cc6efdty3b...@sharklasers.com> ---
Created attachment 168576
  --> https://bugs.kde.org/attachment.cgi?id=168576=edit
crash dump kf 6.1 + patch

I am afraid kate's still crashing for me after the patch [1] :\
Here's a fresh crash dump, with:
Qt: 6.7.0
kf: 6.1.0 (+patch)
kate: 24.02.2

[1]
https://gitlab.archlinux.org/archlinux/packaging/packages/ktexteditor/-/commit/d0302d9de43b1e81d99b76c60f9cfe5f5f8bde52

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

[frameworks-bluez-qt] [Bug 485618] plasmashell crash when Bluez hangs

[mydarkstar]

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

--- Comment #3 from mydarkstar  ---
Thread 1 (Thread 0x76d8b35d01c0 (LWP 1695)):
[KCrash Handler]
#5  0x76d8b95b1629 in
QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*,
QQmlRefPointer const&, QObject*, QV4::String*,
QFlags, QV4::Value const&) () at
/usr/lib/libQt6Qml.so.6
#6  0x76d8b95a713a in QV4::QQmlContextWrapper::virtualPut(QV4::Managed*,
QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt6Qml.so.6
#7  0x76d8b95332a3 in QV4::ExecutionContext::setProperty(QV4::String*,
QV4::Value const&) () at /usr/lib/libQt6Qml.so.6
#8  0x76d8b95cbdc5 in
QV4::Runtime::StoreNameSloppy::call(QV4::ExecutionEngine*, int, QV4::Value
const&) () at /usr/lib/libQt6Qml.so.6
#9  0x76d8b95ff081 in ??? () at /usr/lib/libQt6Qml.so.6
#10 0x76d8b960da95 in ??? () at /usr/lib/libQt6Qml.so.6
#11 0x76d8b9579af8 in ??? () at /usr/lib/libQt6Qml.so.6
#12 0x76d8b95b1df7 in ??? () at /usr/lib/libQt6Qml.so.6
#13 0x76d8b8591599 in ??? () at /usr/lib/libQt6Core.so.6
#14 0x76d853e60d84 in BluezQt::PendingCall::finished(BluezQt::PendingCall*)
() at /usr/lib/libKF6BluezQt.so.6
#15 0x76d853e67488 in ??? () at /usr/lib/libKF6BluezQt.so.6
#16 0x76d8b8591599 in ??? () at /usr/lib/libQt6Core.so.6
#17 0x76d8b93bee90 in ??? () at /usr/lib/libQt6DBus.so.6
#18 0x76d8b857cbb7 in QObject::event(QEvent*) () at
/usr/lib/libQt6Core.so.6
#19 0x76d8ba2f437b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt6Widgets.so.6
#20 0x76d8b853a198 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt6Core.so.6
#21 0x76d8b853a51b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt6Core.so.6
#22 0x76d8b8775ba4 in ??? () at /usr/lib/libQt6Core.so.6
#23 0x76d8b7184199 in g_main_dispatch (context=0x76d8ac000f00) at
../glib/glib/gmain.c:3344
#24 0x76d8b71e33bf in g_main_context_dispatch_unlocked
(context=0x76d8ac000f00) at ../glib/glib/gmain.c:4152
#25 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x76d8ac000f00, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4217
#26 0x76d8b7183712 in g_main_context_iteration (context=0x76d8ac000f00,
may_block=1) at ../glib/glib/gmain.c:4282
#27 0x76d8b8773cd4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#28 0x76d8b85446ee in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#29 0x76d8b853cc38 in QCoreApplication::exec() () at
/usr/lib/libQt6Core.so.6
#30 0x55fa14a58476 in main (argc=, argv=) at
/usr/src/debug/plasma-workspace/plasma-workspace-6.0.3/shell/main.cpp:214

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

[frameworks-bluez-qt] [Bug 485618] plasmashell crash when Bluez hangs

[mydarkstar]

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

mydarkstar  changed:

   What|Removed |Added

Product|plasmashell |frameworks-bluez-qt
   Assignee|plasma-b...@kde.org |kdelibs-b...@kde.org
Version|6.0.3   |6.0.0
  Component|generic-crash   |general
   Target Milestone|1.0 |---

--- Comment #2 from mydarkstar  ---
The following bug report for Plasma 5.27.7 seems relevant, with *disconnecting*
a Bluetooth device:
https://bugs.kde.org/show_bug.cgi?id=474893

This bug report for Plasma 5.26.5 also *disconnects* a Bluetooth device:
https://bugs.kde.org/show_bug.cgi?id=465031

Lastly, this bug report for Plasma 6.0.1 seems similar, but with *connecting* a
Bluetooth device:
https://bugs.kde.org/show_bug.cgi?id=482565

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

[plasmashell] [Bug 456784] Add time information to night color tooltip

[Natalie Clarius]

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

Natalie Clarius  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/-/commi
   ||t/0ed6ee13bbe9f9b3674fb0df5
   ||e87e7e01b854172
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Natalie Clarius  ---
Git commit 0ed6ee13bbe9f9b3674fb0df5e87e7e01b854172 by Natalie Clarius.
Committed on 16/04/2024 at 03:56.
Pushed by nclarius into branch 'master'.

applets/brightness: show info about night light transition times in tooltip

And drop the exact temperature instead since it's not all that informative.

M  +23   -1applets/brightness/package/contents/ui/main.qml

https://invent.kde.org/plasma/plasma-workspace/-/commit/0ed6ee13bbe9f9b3674fb0df5e87e7e01b854172

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

[dolphin] [Bug 483124] Dolphin Opens Second Instance

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kde] [Bug 484833] Small lines appears below the panel and on the left side

[Bug Janitor Service]

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

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

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

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

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

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

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

[Skanpage] [Bug 483151] Skanpage scans only 75dpi

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[okular] [Bug 484562] Bad rendering of EPS embedded in DVI at certain zoom levels

[Bug Janitor Service]

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

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

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

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

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

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

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

[okular] [Bug 484547] Does not show drop down menu in formular

[Bug Janitor Service]

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

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

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

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

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

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

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

[kwin] [Bug 483229] Sometimes unable to bring background apps to the front while Chrome/Chromium is running

[Bug Janitor Service]

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

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

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

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

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

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

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

[dolphin] [Bug 484414] highlight split panel borders when split view actived

[Bug Janitor Service]

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

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

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

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

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

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

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

[plasmashell] [Bug 482811] On X11 with NVIDIA GPU panel always moves moved from one screen to another one after screen unlock

[Bug Janitor Service]

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

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

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

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

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

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

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

[kdenlive] [Bug 463518] can not maximize the kdenlive window

[Bug Janitor Service]

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

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

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

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

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

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

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

[plasmashell] [Bug 485610] "Power and Battery" Widget icon does not update when changed via `powerprofilesctl`

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

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

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

[plasmashell] [Bug 485610] "Power and Battery" Widget icon does not update when changed via `powerprofilesctl`

[Bug Janitor Service]

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

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

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

[plasmashell] [Bug 485610] "Power and Battery" Widget icon does not update when changed via `powerprofilesctl`

[Natalie Clarius]

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

Natalie Clarius  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |natalie_clar...@yahoo.de

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

[kate] [Bug 466175] Feature request: ruff integration for Python

[Bug Janitor Service]

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

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/utilities/kate/-/merge_requests/1461

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

[plasmashell] [Bug 485618] plasmashell crash when Bluez hangs

[mydarkstar]

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

--- Comment #1 from mydarkstar  ---
Created attachment 168575
  --> https://bugs.kde.org/attachment.cgi?id=168575=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 485618] New: plasmashell crash when Bluez hangs

[mydarkstar]

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

Bug ID: 485618
   Summary: plasmashell crash when Bluez hangs
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: mds_f...@protonmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.3)

Qt Version: 6.6.3
Frameworks Version: 6.0.0
Operating System: Linux 6.6.21-273-tkg-linux-lts-tkg-bmq x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.0.3 [CoredumpBackend]

-- Information about the crash:
I more or less accidentally clicked the "Enable Bluetooth" toggle in the
Bluetooth applet while listening to music via Bluetooth.

The Bluetooth headphones got disconnected, but Plasma still showed them as
connected, including a list of other devices, even though it showed the
Bluetooth toggle as disabled.
Pipewire also continued to play the music via the disconnected device, which
was visible in the Audio Volume applet.

When trying to restart `bluetooth.service` via systemctl, plasmashell promptly
crashed.
`bluetooth.service` also would not stop when executing the restart command. I
had to kill it.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  0x76d8b95b1629 in
QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*,
QQmlRefPointer const&, QObject*, QV4::String*,
QFlags, QV4::Value const&) () at
/usr/lib/libQt6Qml.so.6
#6  0x76d8b95a713a in QV4::QQmlContextWrapper::virtualPut(QV4::Managed*,
QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt6Qml.so.6
#7  0x76d8b95332a3 in QV4::ExecutionContext::setProperty(QV4::String*,
QV4::Value const&) () at /usr/lib/libQt6Qml.so.6
#8  0x76d8b95cbdc5 in
QV4::Runtime::StoreNameSloppy::call(QV4::ExecutionEngine*, int, QV4::Value
const&) () at /usr/lib/libQt6Qml.so.6
#9  0x76d8b95ff081 in ??? () at /usr/lib/libQt6Qml.so.6


Reported using DrKonqi

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

[plasmashell] [Bug 483008] Turning off external monitor causes kwin crash

[agapp11]

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

--- Comment #25 from agap...@hotmail.com  ---
Any update on this? It is quite bothersome to have your desktop and apps crash
every time you wake from sleep? Is there anything else I need to include?
Perhaps another backtrace?

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

[frameworks-solid] [Bug 485617] Can't mount encrypted drives

[Edmund Laugasson]

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

--- Comment #2 from Edmund Laugasson  ---
At the same time Gnome Disks under KDE does unlock and mount as regular user.
KDE Partition Manager does as well but as it requires superuser credentials,
not usable for regular user.

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

[frameworks-solid] [Bug 485617] Can't mount encrypted drives

[Edmund Laugasson]

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

--- Comment #1 from Edmund Laugasson  ---
In system dock it says: not enough permissions. Sometimes says nothing - just
won't unlock and mount.
in Dolphin it says: Object does not exist at path "/"
When opening Dolphin via CLI, it says nothing when trying to unlock
LUKS-encrypted USB-drive.

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

[systemsettings] [Bug 451576] Time input field is nightmare

[Natalie Clarius]

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

Natalie Clarius  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/-/commi
   ||t/426c82ef2a192c24015e83b46
   ||75a9ec708650b43
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Natalie Clarius  ---
Git commit 426c82ef2a192c24015e83b4675a9ec708650b43 by Natalie Clarius.
Committed on 16/04/2024 at 02:00.
Pushed by nclarius into branch 'master'.

kcms/nightcolor: use spinboxes instead of text field for manual time selection

The old regex validated text field input method was very cumbersome to use and
buggy.

M  +70   -31   kcms/nightlight/ui/TimeField.qml
M  +2-19   kcms/nightlight/ui/main.qml

https://invent.kde.org/plasma/plasma-workspace/-/commit/426c82ef2a192c24015e83b4675a9ec708650b43

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

[frameworks-solid] [Bug 485617] New: Can't mount encrypted drives

[Edmund Laugasson]

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

Bug ID: 485617
   Summary: Can't mount encrypted drives
Classification: Frameworks and Libraries
   Product: frameworks-solid
   Version: 6.1.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: major
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: edmund.laugas...@protonmail.ch
CC: 31...@tuta.io, ahjoli...@yahoo.com,
amanita+kdeb...@mailbox.org, ctrlal...@gmail.com,
edmund.laugas...@protonmail.ch, fab...@ritter-vogt.de,
gc...@mailbox.org, kdelibs-b...@kde.org,
lu...@kde.org, n...@kde.org, nicolas.fe...@gmx.de,
pvdve...@posteo.net, robby.engelm...@r-engelmann.de,
unassigned-b...@kde.org
Depends on: 477915
  Target Milestone: ---

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

SUMMARY
When to try mount an encrypted drive (LUKS2 + EXT4) either via system dock or
in Dolphin, instead of the password prompt and mounting as regular user,
nothing happens. Sometimes also claims about missing permissions.

After unlocking the drive with cryptsetup through konsole, there is possible to
mount it in Dolphin or via system dock. Also using GNOME Disks or KDE Partition
Manager for unlocking works.

I tried this on Endeavour OS system.


STEPS TO REPRODUCE
1. Have an encrypted storage device plugged in via USB
2. Try to open applet from system dock, which will pop-up when drive is
connected or also file manager Dolphin
3. Click on the encrypted drive in the places panel in the devices section or
also try to click on the pop-up panel in system dock to unlock and mount.

OBSERVED RESULT
Does not unlock and mount as regular user and says: not sufficient permissions.

EXPECTED RESULT
Password prompt pops up, after encrypted drive password is entered as regular
user successfully, drive gets mounted, even user is not in wheel or sudo group.

SOFTWARE/OS VERSIONS
Operating System: Endeavour OS
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.5-arch1-1 (64-bit)
Graphics Platform: X11 (under Wayland systray icon did not open at all)

solid version: 6.1.0-1
solid5 version: 5.115.0-1
udisks2: version 2.10.1-4

ADDITIONAL INFORMATION
When booted from EndeavourOS_Galileo-Neo-2024.01.25.iso as live session then
there was possible to unlock and mount via system dock.


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=477915
[Bug 477915] Can't mount encrypted drives
-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-solid] [Bug 477915] Can't mount encrypted drives

[Edmund Laugasson]

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

Edmund Laugasson  changed:

   What|Removed |Added

 Blocks||485617


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=485617
[Bug 485617] Can't mount encrypted drives
-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 485616] Audio devices suddenly stop working.

[Konstantin]

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

--- Comment #1 from Konstantin  ---
Created attachment 168574
  --> https://bugs.kde.org/attachment.cgi?id=168574=edit
vid

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

[kde] [Bug 485616] New: Audio devices suddenly stop working.

[Konstantin]

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

Bug ID: 485616
   Summary: Audio devices suddenly stop working.
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jon9...@gmail.com
  Target Milestone: ---

Suddenly, audio devices begin to disappear and immediately appear. The devices
disappear for a few seconds and appear (I recorded a video using Spectacle and
because of the dynamic frame rate it is not so noticeable).

Along with this, all audio devices stop working. only a reboot helps.

It happens most often when I stream in OBS and play games. What is the reason
is unclear.

The sound is set like this:
paru -S pipewire lib32-pipewire pipewire-pulse pipewire-alsa pipewire-jack
wireplumber
systemctl --user enable --now pipewire pipewire-pulse wireplumber

Sound Card: Creative Sound Blaster Z

Operating System: Arch Linux 
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × Intel® Core™ i9-14900KF
Memory: 62.6 ГиБ of RAM
Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2
Manufacturer: ASUS

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

[krita] [Bug 457957] Group transformations snap back to original location in preview when containing a filter layer.

[Ralek Kolemios]

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

--- Comment #2 from Ralek Kolemios  ---
Can still confirm this in 5.3 prealpha, though it manifests slightly
differently.
The original transformation of group 31 finishes correctly now, but undoing the
operation afterwards doesn't update the canvas. (The undo does still work
behind the scenes, like in the original report)
Move tool is still non-functional on Group 31.

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

[plasmashell] [Bug 483205] Rapidly moving the pointer over categories causes Plasma to lag and eventually freeze if you keep doing it

[MScattolin]

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

MScattolin  changed:

   What|Removed |Added

 CC||matheus.scattolinanselmo@ou
   ||tlook.com

--- Comment #9 from MScattolin  ---
*** Bug 485136 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 485136] Quickly mouse-hovering kickoff's sidebar momentarily freezes plasma and leaks memory

[MScattolin]

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

MScattolin  changed:

   What|Removed |Added

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

--- Comment #1 from MScattolin  ---


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

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

[krita] [Bug 428317] Tracking rulers update at <1 FPS when non brush tool selected.

[Ralek Kolemios]

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

--- Comment #3 from Ralek Kolemios  ---
In 5.3 this no longer seems to be an issue, either the ruler updates at correct
speed with drawing tools, or it doesn't show at all (for tools in which I feel
there's no need for a ruler, such as the paint bucket or eye dropper. I think
it can be closed.

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

[krita] [Bug 485574] Recorder states it's recording, but isn't.

[Ralek Kolemios]

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

--- Comment #2 from Ralek Kolemios  ---
(In reply to Freya Lupen from comment #1)
> Could that have been the cause here?

That does seem plausible, I rewatched the recording but unfortunately it
started after I had already supposedly just opened the file. It's possible that
right before the recording I may have created or opened a document and then
closed it. I'll keep that in mind when I'm on master.

I recreated the bug you were talking about, and the symptoms seem to be the
same- green dot never turns red, but docker appears as if it's recording.

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

[Powerdevil] [Bug 457859] Powerdevil does not respect sleep inhibitors created with systemd-inhibit by unprivileged users

[Natalie Clarius]

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

--- Comment #13 from Natalie Clarius  ---
I can't reproduce the comment described in the original post either.

As for https://bugs.kde.org/show_bug.cgi?id=457859#c2; sleep inhibitions not
being respected on lid close would be a different issue and best discussed in a
separate bug report. However I would consider this behavior intentional. I
think that inhibition makes sense for preventing the computer from
*automatically* going to sleep when the system is considered idle because no
user activity is detected while there actually is activity, e.g. watching a
video. When the user closes the lid or presses the power button, this is an
intentional action so I would expect the system to go to sleep anyway. 

> If the user wants to just inhibit the lid close action, then they should 
> inhibit "handle-lid-switch". I would like to use that so I can take my laptop 
> from room to room, while it is still running, without having to carry it with 
> the screen open - it is mighty uncomfortable and as far as I know this was 
> the original impetus for inhibiting. 

There is no user-facing setting for this though.

> If the user wants to just inhibit the lid close action, then they should 
> inhibit "handle-lid-switch". I would like to use that so I can take my laptop 
> from room to room, while it is still running, without having to carry it with 
> the screen open - it is mighty uncomfortable and as far as I know this was 
> the original impetus for inhibiting. 

This seems like a bit of a corner case to me: Having the system configured to
sleep on lid close and having an active inhibition ongoing and carrying the
laptop to a different room and not wanting to keep it open by doing so. Imo,
the slight inconvenience of having to keep the laptop open in this scenario is
outweighed by the effects that blocking sleep unconditionally would have. A
user might close their laptop to carry it in their bag, expecting it to go to
sleep, and instead the machine would keep running, potentially causing it to
overheat.

> Specifically, when I toggle the "Manually block sleep and screen locking" 
> button in the PowerDevil Plasma widget, I expect my computer to not sleep for 
> any reason - including closing the laptop lid or pressing the suspend key.

Fwiw, the wording for this in the applet has just been clarified; the
inhibition section now has a caption which reads "Automatic Sleep and and
Screen Locking after Inactivity".

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

[knights] [Bug 429654] Cant's disable voice

[Mark Capella]

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

--- Comment #5 from Mark Capella  ---
Sure! It looks like this changeset:
https://invent.kde.org/markcapella/knights/-/commit/fe457fe5af3b99e59206dfb6e2d266ccc264cbce

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

[plasmashell] [Bug 483163] On X11 with compositing turned on, blank screen on lock screen when using Breeze Plasma style

[bugzilla_noreply]

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

nathan.w.pul...@gmail.com changed:

   What|Removed |Added

 CC||nathan.w.pul...@gmail.com

--- Comment #26 from nathan.w.pul...@gmail.com ---
I am experiencing this bug on KDE Plasma 6 on Garuda Linux on a Lenovo Yoga
laptop with an AMD processor. If I toggle the tty, the lock screen works again.
In other words: lock (by sleep or manually locking) --> black screen with
cursor ---> Ctrl-Alt-F1(screen stays black, cursor is
gone)--->Ctrl-Alt-F2--->Lock screen is back and can log in normally. My theme
is catppuccin Macchiato teal and my icons are Beautyline.

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

[krunner] [Bug 485615] New: KRunner fails to open with shortcut

[Natalie Clarius]

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

Bug ID: 485615
   Summary: KRunner fails to open with shortcut
Classification: Plasma
   Product: krunner
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: natalie_clar...@yahoo.de
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

STEPS TO REPRODUCE
1.  Press Alt+F2

OBSERVED RESULT
Brief flash of a KRunner sized window at the top of the screen, which then
appears 

EXPECTED RESULT
KRunner opens

SOFTWARE/OS VERSIONS
git master
X11
Qt 6.6.3

ADDITIONAL INFORMATION
It works fine when launching KRunner from the terminal.

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

[frameworks-kirigami] [Bug 484888] Kirigami.Icon is blurry when used as a CompactRepresentation in a plasmoid (with floating panel)

[bugzilla_noreply]

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

--- Comment #8 from fi...@tutanota.com ---
I notice this issue is also happening with the icons on the buttons in the
clipboard entry editing area, System Tray → Clipboard → Edit contents.

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Shmerl]

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

--- Comment #40 from Shmerl  ---
> tokenBuffer now gets resized to fit the content

If that's the case - then great! May be your patch will just work then.

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Shmerl]

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

--- Comment #39 from Shmerl  ---
(In reply to Christian Muehlhaeuser from comment #38)
> (In reply to Shmerl from comment #35)
> > Well, I see it being used at least in a few places in the code:
> > 
> > ```
> > src/Vt102Emulation.cpp:322:tokenBufferPos = qMin(tokenBufferPos,
> > MAX_TOKEN_LENGTH - 1);
> > src/Vt102Emulation.h:127:#define MAX_TOKEN_LENGTH 256 // Max length of
> > tokens (e.g. window title)
> > src/Vt102Emulation.h:132:uint tokenBuffer[MAX_TOKEN_LENGTH]; // FIXME:
> > overflow?
> > ```
> 
> That looks like an outdated version of the code. Looking at the git history,
> it seems like this issue may have been fixed a few weeks ago and the
> tokenBuffer now gets resized to fit the content. I've got to take a closer
> look, but that might enable me to revisit this issue. Either way
> MAX_TOKEN_LENGTH is definitely obsolete now.

Right, I should have clarified, I was doing it with Debian testing's konsole
which is behind recent versions (due to Debian being in the middle of time_t
64-bit migration monstrosity and KDE maintainers not updating things often).

https://tracker.debian.org/pkg/konsole

But that's regardless, if the new code isn't using that define, it's still
might have the limit somewhere. So you can get the idea what can be increased?

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Christian Muehlhaeuser]

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

--- Comment #38 from Christian Muehlhaeuser  ---
(In reply to Shmerl from comment #35)
> Well, I see it being used at least in a few places in the code:
> 
> ```
> src/Vt102Emulation.cpp:322:tokenBufferPos = qMin(tokenBufferPos,
> MAX_TOKEN_LENGTH - 1);
> src/Vt102Emulation.h:127:#define MAX_TOKEN_LENGTH 256 // Max length of
> tokens (e.g. window title)
> src/Vt102Emulation.h:132:uint tokenBuffer[MAX_TOKEN_LENGTH]; // FIXME:
> overflow?
> ```

That looks like an outdated version of the code. Looking at the git history, it
seems like this issue may have been fixed a few weeks ago and the tokenBuffer
now gets resized to fit the content. I've got to take a closer look, but that
might enable me to revisit this issue. Either way MAX_TOKEN_LENGTH is
definitely obsolete now.

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

[dolphin] [Bug 485614] New: [FEATURE REQUEST] Allow navigation of dolphin while dragging and dropping a file.

[Ali]

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

Bug ID: 485614
   Summary: [FEATURE REQUEST] Allow navigation of dolphin while
dragging and dropping a file.
Classification: Applications
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: radical...@proton.me
CC: kfm-de...@kde.org
  Target Milestone: ---

== WISHLIST / FEATURE REQUEST ==

SUMMARY
Allow navigation through folders, tabs and side panel shortcuts while dragging
and dropping by simply hovering over said objects for a few seconds. This
behaviour is in Nautilus and Finder, and makes navigating subdirectories while
dragging and dropping files to be less of a painful maneuver. 

STEPS TO REPRODUCE
1. Drag any file
2. Hover over any folder, tab, or side panel shortcut

OBSERVED RESULT
You keep holding the file instead of entering the directory 

EXPECTED RESULT
You enter the directory after a few seconds of holding the drag and dropped
file.

ADDITIONAL INFORMATION
Make this a configurable option if possible, maybe even make the time it takes
for a directory to be entered from the hover state be changeable?

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

[Haruna] [Bug 484121] CJK Bold font is difficult to read

[george fb]

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

george fb  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/mult
   ||imedia/haruna/-/commit/2705
   ||1ee4f77512ce2f5c58294e452b3
   ||ea0ff8fa3
 Resolution|--- |FIXED

--- Comment #1 from george fb  ---
Git commit 27051ee4f77512ce2f5c58294e452b3ea0ff8fa3 by George Florea Bănuș.
Committed on 15/04/2024 at 22:59.
Pushed by georgefb into branch 'master'.

PlayListItem(WithThumbnail): don't make playing item bold

M  +0-1src/qml/PlayListItem.qml
M  +0-1src/qml/PlayListItemWithThumbnail.qml

https://invent.kde.org/multimedia/haruna/-/commit/27051ee4f77512ce2f5c58294e452b3ea0ff8fa3

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

[Discover] [Bug 485613] Discover crashes when you search into all apps

[smow]

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

smow  changed:

   What|Removed |Added

 CC||smowten...@protonmail.com

--- Comment #1 from smow  ---
I can reproduce it with the following backtrace

Application: Discover (plasma-discover), signal: Segmentation fault


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.
[New LWP 68361]
[New LWP 68362]
[New LWP 68371]
[New LWP 68370]
[New LWP 68382]
[New LWP 68381]
[New LWP 68380]
[New LWP 68413]
[New LWP 68363]
[New LWP 68392]
[New LWP 68364]
[New LWP 68369]
[New LWP 68394]
[New LWP 68384]
[New LWP 68390]
[New LWP 68393]
[New LWP 68395]
[New LWP 68388]
[New LWP 68389]
[New LWP 68397]
[New LWP 68391]
[New LWP 68383]
[New LWP 68398]
[New LWP 68385]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasma-discover'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x6fffd76ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x6fffd31649c0 (LWP 68361))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x6fffd31649c0 (LWP 68361))]

Thread 24 (Thread 0x6fff8fe006c0 (LWP 68385)):
#0  0x6fffd76a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x6fffd76a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x6fffd7eb8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x6fffd7eb2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x6fffd7eadcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x6fffd76a955a in ??? () at /usr/lib/libc.so.6
#6  0x6fffd7726a3c in ??? () at /usr/lib/libc.so.6

Thread 23 (Thread 0x6fff774006c0 (LWP 68398)):
#0  0x6fffd76a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x6fffd76a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x6fffd7eb8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x6fffd7eb2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x6fffd7eadcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x6fffd76a955a in ??? () at /usr/lib/libc.so.6
#6  0x6fffd7726a3c in ??? () at /usr/lib/libc.so.6

Thread 22 (Thread 0x6fff998006c0 (LWP 68383)):
#0  0x6fffd77190bf in poll () at /usr/lib/libc.so.6
#1  0x6fffd6f31306 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x6fffd6ed2dc7 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x6fffd61ec83c in ??? () at /usr/lib/libgio-2.0.so.0
#4  0x6fffd6f00065 in ??? () at /usr/lib/libglib-2.0.so.0
#5  0x6fffd76a955a in ??? () at /usr/lib/libc.so.6
#6  0x6fffd7726a3c in ??? () at /usr/lib/libc.so.6

Thread 21 (Thread 0x6fff8d6006c0 (LWP 68391)):
#0  0x6fffd76a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x6fffd76a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x6fffd7eb8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x6fffd7eb2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x6fffd7eadcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x6fffd76a955a in ??? () at /usr/lib/libc.so.6
#6  0x6fffd7726a3c in ??? () at /usr/lib/libc.so.6

Thread 20 (Thread 0x6fff77e006c0 (LWP 68397)):
#0  0x6fffd76a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x6fffd76a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x6fffd7eb8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x6fffd7eb2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x6fffd7eadcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x6fffd76a955a in ??? () at /usr/lib/libc.so.6
#6  0x6fffd7726a3c in ??? () at /usr/lib/libc.so.6

Thread 19 (Thread 0x6fff8ea006c0 (LWP 68389)):
#0  0x6fffd77190bf in poll () at /usr/lib/libc.so.6
#1  0x6fffd180d936 in ??? () at /usr/lib/libnvidia-egl-wayland.so.1
#2  0x6fffd76a955a in ??? () at /usr/lib/libc.so.6
#3  0x6fffd7726a3c in ??? () at /usr/lib/libc.so.6

Thread 18 (Thread 0x6fff8f4006c0 (LWP 68388)):
#0  0x6fffd76a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x6fffd76a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x6fffcbab9c38 in ??? () at /usr/lib/libEGL_nvidia.so.0
#3  0x6fffcba8a4c1 in ??? () at /usr/lib/libEGL_nvidia.so.0
#4  0x6fffcbabfcce in ??? () at /usr/lib/libEGL_nvidia.so.0
#5  0x6fffd76a955a in ??? () at /usr/lib/libc.so.6
#6  0x6fffd7726a3c in ??? () at /usr/lib/libc.so.6

Thread 17 (Thread 0x6fff810006c0 (LWP 68395)):
#0  0x6fffd77190bf in poll () at /usr/lib/libc.so.6
#1  0x6fffca5f69d7 in ??? () at /usr/lib/libnvidia-eglcore.so.550.67
#2  0x6fffca5f4f8a 

[Discover] [Bug 485613] Discover crashes when you search into all apps

[Jon Intxaurbe]

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

Jon Intxaurbe  changed:

   What|Removed |Added

 CC||join...@gmail.com

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

[Discover] [Bug 485613] New: Discover crashes when you search into all apps

[Jon Intxaurbe]

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

Bug ID: 485613
   Summary: Discover crashes when you search into all apps
Classification: Applications
   Product: Discover
   Version: 6.0.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: join...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
when you open Discover and you select something to search (for example,
Thunderbird) the search is completed, but after a few seconds, Discover
crashes. Not error's report is shown. I don't know how debug, I'm sorry.
However, if you chose some category and search something, it doesn't crash. 

STEPS TO REPRODUCE
1. Open Discover
2. Search something (something which could be in the database. F.i.
Thunderbird). Curiously, with some terms, it doesn't crashes. I think that if
the search is for an app's complete name, it's when Discover crashes.
3. After show the results, wait 5 seconds more or less for crashing.

SOFTWARE/OS VERSIONS
KDE Neon, updated to Plasma 6 from Plasma 5
Linux/KDE Plasma: 6.5.0-27-generic (64-bit)
(available in About System)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
wayland

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Shmerl]

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

--- Comment #37 from Shmerl  ---
So I'd say it's worth looking into that, or even making this buffer dynamic
when you need to handle osc52 altogether and set some limits which are defined
separately.

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Shmerl]

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

--- Comment #36 from Shmerl  ---
It's definitely helping! I was able to copy 27,637 bytes now when testing
copying some random text, unlike without the patch.

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

[Haruna] [Bug 480535] Add Gif support (should be supported by libmpv)

[george fb]

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

george fb  changed:

   What|Removed |Added

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

--- Comment #1 from george fb  ---
I'd rather not start adding support for images.

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Shmerl]

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

--- Comment #35 from Shmerl  ---
Well, I see it being used at least in a few places in the code:

```
src/Vt102Emulation.cpp:322:tokenBufferPos = qMin(tokenBufferPos,
MAX_TOKEN_LENGTH - 1);
src/Vt102Emulation.h:127:#define MAX_TOKEN_LENGTH 256 // Max length of tokens
(e.g. window title)
src/Vt102Emulation.h:132:uint tokenBuffer[MAX_TOKEN_LENGTH]; // FIXME:
overflow?
```

But I didn't dig extensively through it. Trying to build it now with that
change to see if it does anything.

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Christian Muehlhaeuser]

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

--- Comment #34 from Christian Muehlhaeuser  ---
(In reply to Shmerl from comment #33)
> Apparently some downstream distros are working around this by changing the
> buffer size:
> 
> -#define MAX_TOKEN_LENGTH 256 // Max length of tokens (e.g. window title)
> +#define MAX_TOKEN_LENGTH 65536 // Max length of tokens (e.g. window title)

I'm surprised to hear that, as I don't think changing this constant actually
has any effect. It looks like a remnant that was forgotten to be removed and
it's not actually used anywhere.

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

[kdeconnect] [Bug 479464] Running command doesn't work when there are spaces in the command

[bugzilla_noreply]

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

tremo...@muskelshirt.de changed:

   What|Removed |Added

 CC||tremo...@muskelshirt.de

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

[kde] [Bug 485612] New: System tray popups get minimized after maximizing an application.

[Nikki]

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

Bug ID: 485612
   Summary: System tray popups get minimized after maximizing an
application.
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: cerv...@protonmail.com
  Target Milestone: ---

Created attachment 168573
  --> https://bugs.kde.org/attachment.cgi?id=168573=edit
Minimized popup

SUMMARY
Using the default panel with the position set to the bottom edge and its style
set to floating and using the system tray widget inside of it. 
When maximizing an application, the panel will move to the bottom of the
screen, instead of having a slight offset from the bottom. This is expected and
working. But what happened in the background, is that all expandable popups (a
popup you see when clicking on of the system tray's icons), now are minimized
to a basically invisible square. I have to click on the pixel where the popup
is and then use my mouse and click and drag to expand it, to make it visible
again. This is definitely not intended and a bug. 

STEPS TO REPRODUCE
1. Add a default panel to the bottom of the screen and set its style to
floating.
2. Maximize any application.

OBSERVED RESULT
System tray icon's popups are now completely minimized, though can be fixed by
expanding them using the mouse. 

EXPECTED RESULT
System tray icon's popups should be fully visible, with its usual size.

SOFTWARE/OS VERSIONS
Linux: 6.8.5-arch1-1
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

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

[kdeconnect] [Bug 479464] Running command doesn't work when there are spaces in the command

[bugzilla_noreply]

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

tremo...@muskelshirt.de changed:

   What|Removed |Added

 CC||blahblahbr...@protonmail.co
   ||m

--- Comment #1 from tremo...@muskelshirt.de ---
*** Bug 483426 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 483426] Run Commands stopped working after updating the client

[bugzilla_noreply]

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

tremo...@muskelshirt.de changed:

   What|Removed |Added

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

--- Comment #2 from tremo...@muskelshirt.de ---


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

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

[kdeconnect] [Bug 483426] Run Commands stopped working after updating the client

[bugzilla_noreply]

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

--- Comment #1 from tremo...@muskelshirt.de ---
I was using the shutdown command on Windows: shutdown /t 30 /s
No longer works, since at least a month.

Using KDE Connect from Microsoft Store with the Android app from Play Store.

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Shmerl]

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

--- Comment #33 from Shmerl  ---
Apparently some downstream distros are working around this by changing the
buffer size:

-#define MAX_TOKEN_LENGTH 256 // Max length of tokens (e.g. window title)
+#define MAX_TOKEN_LENGTH 65536 // Max length of tokens (e.g. window title)

That might cover all cases (like very large selections) but it's still better
than 256 characterless. Is there a problem to changing that default to
something like a few megabytes altogether?

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

[kwin] [Bug 484861] Crash when starting plasma mobile

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/-/commit/3ed535dd67
   ||29263fbeac3d77607126b22500a
   ||b05

--- Comment #2 from David Edmundson  ---
Git commit 3ed535dd6729263fbeac3d77607126b22500ab05 by David Edmundson.
Committed on 15/04/2024 at 22:03.
Pushed by davidedmundson into branch 'master'.

Remove superfluous wake in dpmsinputeventfilter destruction

Workspace already makes sure to only dynamically delete the
dpmsinputeventfilter if all screens are currently on. This line to wake
all screens is therefore redundant.

It's problematic as it can cause a crash on final teardown when
workspace is destroyed.

M  +0-1src/dpmsinputeventfilter.cpp

https://invent.kde.org/plasma/kwin/-/commit/3ed535dd6729263fbeac3d77607126b22500ab05

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

[frameworks-solid] [Bug 477915] Can't mount encrypted drives

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

Version|6.1.0   |5.246.0

--- Comment #17 from Nicolas Fella  ---
See https://bugs.kde.org/show_bug.cgi?id=485507

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

[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Priority|NOR |HI

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

[Discover] [Bug 484901] Indicate whether reboot is needed in system tray icon

[tqd8]

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

--- Comment #1 from tqd8  ---
Oh wait, to be clear: I mean to indicate a required restart in Discover's icon
itself *even before* installation. I know we have a separate icon (that said,
do some distros not use it?) for indicating a restart is required after
installation. However I think that one could also be combined into Discover's
circled-up-arrow icon rather than being separate.

Hope this makes sense?

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

[frameworks-solid] [Bug 477915] Can't mount encrypted drives

[Nate Graham]

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

--- Comment #16 from Nate Graham  ---
FWIW I just encountered the issue this morning. No time to debug it right now
as I am boarding a plane in 20 minutes; will comment in the new bug report. Can
you file one and mention it here, Edmund?

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

[kdenlive] [Bug 485611] New: Bad Version Number after install

[Simon Fonteneau]

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

Bug ID: 485611
   Summary: Bad Version Number after install
Classification: Applications
   Product: kdenlive
   Version: 24.02.2
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Installation
  Assignee: j...@kdenlive.org
  Reporter: sfonten...@tranquil.it
  Target Milestone: ---

On website
(https://download.kde.org/stable/kdenlive/24.02/windows/kdenlive-24.02.2.exe)
The version windows here does not appear to be version 24.02.2 , after install
--> 24.02.1

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

[KBibTeX] [Bug 484418] Support for searching and adding book citations (e.g. from Google Books, WorldCat)

[Thomas Fischer]

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

Thomas Fischer  changed:

   What|Removed |Added

  Latest Commit|8e723e9f3cf7b0f8b9895edeb6b |ffe0fb736ac6a377b772bc6f5a7
   |83147c4e4033c   |b7edb0e004b18

--- Comment #3 from Thomas Fischer  ---
(In reply to Adam Fontenot from comment #2)
> Thanks for working on this! It took some effort to build against Qt6, but I
> did succeed and all the books I've tried so far are working.
KBibTeX's master branch (still) supports Qt5 and Qt6 equally well, so you can
continue to use it with your existing KF5 installation.

> It probably makes sense to synthesize an ID field rather than using the
> Google Books ones that look like "GoogleBooks:fnG8BAAAQBAJ".
Ok, changed to use the ISBN.
> The URL field has a bunch of useless stuff in it, all of the following links
> for this book are previews of the book:
>[..]
> It would be better to link to the official Google Books page, even if the
> link has to be synthesized: https://books.google.com/books?id=fnG8BAAAQBAJ
Fixed.

There were some other issues and bugs I fixed as well. I also noted that Google
Books allows to download BibTeX code directly via another URL, but the data,
even for the same book, is not the same. Thus, this revised search uses both
sources/methods and then merges the results.

I made a force-push, in case you wonder.

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

[plasma-pa] [Bug 485399] Feature Request: Native PipeWire graph control

[tqd8]

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

--- Comment #4 from tqd8  ---
I was just thinking about discoverability (people may not know it exists) and a
more streamlined implementation built right into the interface. Could still
download qpwgraph for more control either way.

Or maybe we could add a small indicator saying that graph apps are available,
like in https://invent.kde.org/system/dolphin/-/merge_requests/674 or the
browser integration?

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

[digikam] [Bug 485591] Many windows, UI elements are unusably small on high DPI screens

[Maik Qualmann]

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

--- Comment #12 from Maik Qualmann  ---
Your toolbar and tool sidebar icons are too small. It is possible to choose a
smaller icon size for the toolbar. I have no idea about the tool sidebar.

A test here with a native Wayland Desktop session shows me no different view
than with X11.

Maik

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

[plasmashell] [Bug 483188] With AMD GPU and non-floating panel, Icons-Only Task Manager on one monitor's panel randomly becomes unresponsive until plasmashell is restarted or a window is maximized and

[bugzilla_noreply]

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

--- Comment #26 from yuraposta...@proton.me ---
> Interesting. What distro are you on and do you use any non-default options?
> I have middle-click set to close windows and I turn off "Mark applications
> that play audio". Everything else is default IIRC.

Arch Linux. I have the default options afaik. I have middle click set to Opens
a new window and Mark applications that play audio is turned on

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

[digikam] [Bug 485591] Many windows, UI elements are unusably small on high DPI screens

[Barnaby]

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

--- Comment #11 from Barnaby  ---
I added some reference screenshots launching digiKam with QT_SCALE_FACTOR=1.5.
Generally speaking the sizes of icons and UI elements is better, but default
window sizes and icon spacing are just as bad. I changed the application font
size to 9 which improves things slightly, but it’s still borderline unusable
IMO.

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

[digikam] [Bug 485591] Many windows, UI elements are unusably small on high DPI screens

[Barnaby]

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

--- Comment #10 from Barnaby  ---
Created attachment 168572
  --> https://bugs.kde.org/attachment.cgi?id=168572=edit
QT_SCALE_FACTOR=1.5 enlarged image editor window

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

[digikam] [Bug 485591] Many windows, UI elements are unusably small on high DPI screens

[Barnaby]

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

--- Comment #9 from Barnaby  ---
Created attachment 168571
  --> https://bugs.kde.org/attachment.cgi?id=168571=edit
QT_SCALE_FACTOR=1.5 default image editor size

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

[digikam] [Bug 485591] Many windows, UI elements are unusably small on high DPI screens

[Barnaby]

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

--- Comment #8 from Barnaby  ---
Created attachment 168570
  --> https://bugs.kde.org/attachment.cgi?id=168570=edit
QT_SCALE_FACTOR=1.5 photo list

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

[digikam] [Bug 485591] Many windows, UI elements are unusably small on high DPI screens

[Maik Qualmann]

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

--- Comment #7 from Maik Qualmann  ---
This could be a problem with the integration in Wayland with the AppImage.
I'm currently using an X11 desktop with KF6. With a QT_SCALE_FACTOR of 1.5 to
2.0 I have no problems with the AppImage, everything scales and looks good.
Also, for example, the grab handles in the selection tool in the image editor.

Maik

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

[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #8 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/solid/-/merge_requests/163

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

[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows

[Zamundaaa]

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

Zamundaaa  changed:

   What|Removed |Added

 CC||edgar.serrano.9...@gmail.co
   ||m

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

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

[kwin] [Bug 485561] Thin lines below the panel with fractional scaling

[Zamundaaa]

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

Zamundaaa  changed:

   What|Removed |Added

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

--- Comment #3 from Zamundaaa  ---


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

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

[Spectacle] [Bug 485352] DBus timeout on X11

[Noah Davis]

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

--- Comment #1 from Noah Davis  ---
Unfortunately, I cannot reproduce this.

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

[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives

[Marcel Hasler]

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

--- Comment #7 from Marcel Hasler  ---
I've assigned the bug to the author of the commit (I hope that's okay to do).

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

[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives

[Marcel Hasler]

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

--- Comment #6 from Marcel Hasler  ---
Looking at the code some more, it seems that many functions explicitly check
for both cases, e.g. in StorageAccess::filePath():

const QString path = clearTextPath();
if (path.isEmpty() || path == "/") {
QString();
}

Other functions, such as StorageAccess::setup() (which I think might be the
culprit here), don't:

if (m_device->isEncryptedContainer() && clearTextPath().isEmpty()) {
return requestPassphrase();
} else {
return mount();
}

Perhaps it would make sense to refactor this check into an own function (e.g.
StorageAccess::isUnlocked()).

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

[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives

[bugzilla_noreply]

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

--- Comment #5 from verifyrecove...@pm.me ---
Ahh good catch. Should be pretty simple to fix. How can we help the devs? I
don't see an option to raise a PR.

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

[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives

[Marcel Hasler]

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

Marcel Hasler  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |k...@privat.broulik.de

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

[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives

[Marcel Hasler]

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

Marcel Hasler  changed:

   What|Removed |Added

Version|unspecified |6.1.0

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

[plasmashell] [Bug 485610] New: "Power and Battery" Widget icon does not update when changed via `powerprofilesctl`

[Kye]

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

Bug ID: 485610
   Summary: "Power and Battery" Widget icon does not update when
changed via `powerprofilesctl`
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Battery Monitor
  Assignee: plasma-b...@kde.org
  Reporter: kylie...@gmail.com
CC: k...@privat.broulik.de, m...@ratijas.tk,
natalie_clar...@yahoo.de
  Target Milestone: 1.0

SUMMARY


STEPS TO REPRODUCE
1. Install power-profiles-deamon
2. Change the power profile via `powerprofilectl`
3. See that the status icon does not update.

OBSERVED RESULT
Status icon remains in the previous state.

EXPECTED RESULT
Status icon updates to match the current power profile state

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kernel 6.8.5-arch1-1
(available in About System)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

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

[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives

[Marcel Hasler]

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

--- Comment #4 from Marcel Hasler  ---
Downgrading Solid back to 6.0.0 fixes the issue.

Looking at the change log, there's really only one commit
(https://invent.kde.org/frameworks/solid/-/commit/f000b6e99f741c66744a8995f6521e9158ebf289).
I think the problem here is that the property "CleartextDevice" returned from
the new code defaults to '/' if the device hasn't been unlocked yet, whereas
the old code returned an empty string, which clients apparently expect.

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

[Plasma Bigscreen] [Bug 462195] Feature request: Desktop Switchmode Plasma Bigscreen - classic desktop mode

[bugzilla_noreply]

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

villene...@arcor.de changed:

   What|Removed |Added

 CC||villene...@arcor.de

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

[Plasma Bigscreen] [Bug 480929] Plasma Bigscreen fails to start

[bugzilla_noreply]

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

villene...@arcor.de changed:

   What|Removed |Added

 CC||villene...@arcor.de

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

[kdeplasma-addons] [Bug 482914] Ability to type newline or tab in Application Dashboard search field

[bugzilla_noreply]

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

villene...@arcor.de changed:

   What|Removed |Added

 CC||villene...@arcor.de

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

[krunner] [Bug 485606] Baloorunner starts even when baloo is not active

[bugzilla_noreply]

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

tagwer...@innerjoin.org changed:

   What|Removed |Added

 CC||tagwer...@innerjoin.org

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

[kdeplasma-addons] [Bug 483142] [wayland] Pressing Enter on Application Dashboard does not open the selected application

[bugzilla_noreply]

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

villene...@arcor.de changed:

   What|Removed |Added

 CC||villene...@arcor.de

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

[digikam] [Bug 231528] The first photo should not be automatically selected in icon-views

[Maik Qualmann]

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

--- Comment #12 from Maik Qualmann  ---
Git commit 850d82387534651c92672e6609ee382703d0655f by Maik Qualmann.
Committed on 15/04/2024 at 19:52.
Pushed by mqualmann into branch 'master'.

add option to disable select first album item

M  +1-0core/app/items/views/digikamitemview.cpp
M  +2-0core/libs/settings/applicationsettings.cpp
M  +3-0core/libs/settings/applicationsettings.h
M  +10   -0core/libs/settings/applicationsettings_miscs.cpp
M  +4-1core/libs/settings/applicationsettings_p.cpp
M  +3-0core/libs/settings/applicationsettings_p.h
M  +12   -11   core/libs/widgets/itemview/itemviewcategorized.cpp
M  +5-0core/libs/widgets/itemview/itemviewcategorized.h
M  +11   -7core/utilities/setup/misc/setupmisc.cpp
M  +1-0core/utilities/setup/misc/setupmisc_p.h

https://invent.kde.org/graphics/digikam/-/commit/850d82387534651c92672e6609ee382703d0655f

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