[plasmashell] [Bug 489057] When entering plasma panel editing mode, the editing mode jumps out immediately

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

elgoogno...@gmail.com changed:

   What|Removed |Added

   Keywords||wayland

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

[plasmashell] [Bug 489057] When entering plasma panel editing mode, the editing mode jumps out immediately

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

--- Comment #6 from elgoogno...@gmail.com ---
I found one possible culprit!

Traditionally in order to use fcitx input method (e.g. mcbopomofo for
Traditional Chinese in Taiwan) in Wayland + KDE Plasma, we need to go to Plasma
setting/Keyboard/Virtual keyboard and set it to "Fcitx 5"
In the fresh test acccount, of course I did not do this.

Most importantly, for the original erroneous account, after I set Plasma
setting/Keyboard/Virtual keyboard back to "None" (which is default for a new
account), the "Enter edit mode" behavior resumed normal!

Hope this helps.

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

[frameworks-baloo] [Bug 489406] Baloo doesn't automatically index multimedia files' metadata

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

--- Comment #6 from tagwer...@innerjoin.org ---
(In reply to malikth32 from comment #5)
> ... I did these in my original bug report. balooctl6 monitor did not
> return anything even when I manually indexed a file with balooctl6 index ...
Sorry, yes, of course.

I would say it's a bug that it does not pick up files you index manually, it
watches what baloo_file_extractor is doing though and balooctl6 does its
indexing independently

(In reply to malikth32 from comment #5)
> ... what I expected to have happen by default ...
Having content indexing enabled by default? I think that happens normally. It
would be a distro thing though, how they decide to set up the Desktop.

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

[kmymoney] [Bug 489417] Delete Subcategory Greyed out

2024-06-28 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=489417

Thomas Baumgart  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Baumgart  ---
In case the deletion option is greyed out the category is referenced by another
object. Candidates are: schedules, reports.

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

[kwin] [Bug 488941] Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled

2024-06-28 Thread Stephanie
https://bugs.kde.org/show_bug.cgi?id=488941

Stephanie  changed:

   What|Removed |Added

Version|6.1.0   |6.1.1
 CC||ponyosunsh...@gmail.com

--- Comment #8 from Stephanie  ---
I am also experiencing the exact same problem and have found the same temporary
solution to work.

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

[kcalc] [Bug 489339] Using decimals without a leading zero causes input error and not carrying output to inputs

2024-06-28 Thread Christophe Marin
https://bugs.kde.org/show_bug.cgi?id=489339

Christophe Marin  changed:

   What|Removed |Added

 Resolution|UPSTREAM|DUPLICATE

--- Comment #2 from Christophe Marin  ---
(In reply to Gabriel Barrantes from comment #1)
> Duplicate of 487566 & 487659

Let's use the correct resolution then

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

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

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

2024-06-28 Thread Christophe Marin
https://bugs.kde.org/show_bug.cgi?id=487566

Christophe Marin  changed:

   What|Removed |Added

 CC||irongrin...@gmail.com

--- Comment #49 from Christophe Marin  ---
*** Bug 489339 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle

2024-06-28 Thread Miroslav Spehar
https://bugs.kde.org/show_bug.cgi?id=410856

Miroslav Spehar  changed:

   What|Removed |Added

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

--- Comment #14 from Miroslav Spehar  ---
Answered above

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

[Skanpage] [Bug 486771] Extremely slow UI with some driver/compositor combinations

2024-06-28 Thread Guillaume Castagnino
https://bugs.kde.org/show_bug.cgi?id=486771

--- Comment #6 from Guillaume Castagnino  ---
Using strace I saw suspicious USBDEVFS_REAPURBNDELAY ioctl loops even while not
using the scanner, only browsing the interface. So I check ksanecore and guess
what: the bad behaviour is fixed by :
https://invent.kde.org/libraries/ksanecore/-/merge_requests/19

The MR speak about *remote* PIXMA scanner, but this bug can be definitively
linked, even for local USB PIXMA scanner :)

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

[digikam] [Bug 488662] Incorrect Thumbnails showing on scanned Tiff files

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

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

prepare for the switch to a new unique hash
API optimized to be more universal for unique hash functions.

M  +2-6core/libs/database/coredb/coredb.cpp
M  +0-2core/libs/database/coredb/coredb.h
M  +1-1core/libs/database/item/containers/iteminfo_history.cpp
M  +9-7core/libs/database/item/scanner/itemscanner_history.cpp
M  +11   -5core/libs/dimg/dimg.h
M  +27   -11   core/libs/dimg/dimg_metadata.cpp
M  +2-1core/libs/dimg/dimg_p.h

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

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

[plasmashell] [Bug 489419] New: Plasma crash when connecting projector

2024-06-28 Thread APTX
https://bugs.kde.org/show_bug.cgi?id=489419

Bug ID: 489419
   Summary: Plasma crash when connecting projector
Classification: Plasma
   Product: plasmashell
   Version: 6.1.1
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: marek...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.1.1)
 (Compiled from sources)
Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.6.30-gentoo-x86_64 x86_64
Windowing System: Wayland
Distribution: "Gentoo Linux"
DrKonqi: 6.1.1 [CoredumpBackend]

-- Information about the crash:
I have a projector that, when turned on, generates disconnected and connected
events. No event is generated when the projector is turned off.

Sometimes when I turn the projector on, plasma crashes.

The crash can be reproduced sometimes.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[New LWP 6786]
[New LWP 6792]
[New LWP 6791]
[New LWP 6932]
[New LWP 7230]
[New LWP 7454]
[New LWP 6788]
[New LWP 7427]
[New LWP 8758]
[New LWP 11260]
[New LWP 11740]
[New LWP 68115]
[New LWP 8868]
[New LWP 9010]
[New LWP 68116]
[New LWP 11261]
[New LWP 7426]
[New LWP 7425]
[New LWP 8774]
[New LWP 11741]
[New LWP 11739]
[New LWP 11259]
[New LWP 11742]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f73a524bc9c in ?? () from /usr/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f739f775a00 (LWP 6786))]

Cannot QML trace cores :(
Unexpectedly stumbled over an objfile (/usr/bin/plasmashell) without build_id.
Not creating payload.
[Current thread is 1 (Thread 0x7f739f775a00 (LWP 6786))]

Thread 23 (Thread 0x7f733b7fe6c0 (LWP 11742)):
#0  0x7f73a52a9edf in poll () at /usr/lib64/libc.so.6
#1  0x7f73a41408d7 in g_main_context_poll_unlocked (priority=, n_fds=3, fds=0x7f7364001090, timeout=,
context=0x7f737c085900) at ../glib-2.78.6/glib/gmain.c:4653
#2  g_main_context_iterate_unlocked (context=0x7f737c085900,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../glib-2.78.6/glib/gmain.c:4344
#3  0x7f73a414128f in g_main_loop_run (loop=0x7f737c085a30) at
../glib-2.78.6/glib/gmain.c:4551
#4  0x7f739f90d67a in gdbus_shared_thread_func (user_data=0x7f737c0858d0)
at ../glib-2.78.6/gio/gdbusprivate.c:284
#5  0x7f73a416e2f1 in g_thread_proxy (data=0x7f737c063420) at
../glib-2.78.6/glib/gthread.c:831
#6  0x7f73a5249fb2 in ??? () at /usr/lib64/libc.so.6
#7  0x7f73a52b6b6c in ??? () at /usr/lib64/libc.so.6

Thread 22 (Thread 0x7f73818566c0 (LWP 11259)):
#0  0x7f73a52468de in ??? () at /usr/lib64/libc.so.6
#1  0x7f73a52491a2 in pthread_cond_wait () at /usr/lib64/libc.so.6
#2  0x7f739d0ba1e8 in ??? () at /usr/lib64/libEGL_nvidia.so.0
#3  0x7f739d08a661 in ??? () at /usr/lib64/libEGL_nvidia.so.0
#4  0x7f739d0c027e in ??? () at /usr/lib64/libEGL_nvidia.so.0
#5  0x7f73a5249fb2 in ??? () at /usr/lib64/libc.so.6
#6  0x7f73a52b6b6c in ??? () at /usr/lib64/libc.so.6

Thread 21 (Thread 0x7f7373fff6c0 (LWP 11739)):
#0  0x7f73a52a9edf in poll () at /usr/lib64/libc.so.6
#1  0x7f73a41408d7 in g_main_context_poll_unlocked (priority=, n_fds=1, fds=0x7f73680010e0, timeout=,
context=0x7f7368000c60) at ../glib-2.78.6/glib/gmain.c:4653
#2  g_main_context_iterate_unlocked (context=context@entry=0x7f7368000c60,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../glib-2.78.6/glib/gmain.c:4344
#3  0x7f73a4140fa0 in g_main_context_iteration (context=0x7f7368000c60,
may_block=1) at ../glib-2.78.6/glib/gmain.c:4414
#4  0x7f73a56b3581 in QEventDispatcherGlib::processEvents
(this=0x7f7368000ed0, flags=...) at
/usr/src/debug/dev-qt/qtbase-6.7.2/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qeventdispatcher_glib.cpp:396
#5  0x7f73a5903f9a in QEventLoop::exec (this=this@entry=0x7f7373ffeb40,
flags=..., flags@entry=...) at
/usr/src/debug/dev-qt/qtbase-6.7.2/qtbase-everywhere-src-6.7.2/src/corelib/global/qflags.h:34
#6  0x7f73a5840870 in QThread::exec (this=) at
/usr/src/debug/dev-qt/qtbase-6.7.2/qtbase-everywhere-src-6.7.2/src/corelib/global/qflags.h:74
#7  0x7f73a57e20aa in operator() (__closure=) at
/usr/src/debug/dev-qt/qtbase-6.7.2/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:326
#8  (anonymous
namespace)::terminate_on_exception >
(t=) at
/usr/src/debug/dev-qt/qtbase-6.7.2/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:262
#9  QThreadPrivate::start (arg=0x7f737c063500) at
/usr/src/debug/dev-qt/qtbase-6.7.2/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp

[plasmashell] [Bug 489418] New: Odd flicker when moving a file from Dolphin to the desktop for the first time after booting

2024-06-28 Thread Fernando M. Muniz
https://bugs.kde.org/show_bug.cgi?id=489418

Bug ID: 489418
   Summary: Odd flicker when moving a file from Dolphin to the
desktop for the first time after booting
Classification: Plasma
   Product: plasmashell
   Version: 6.1.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: plasma-b...@kde.org
  Reporter: fernandommu...@gmail.com
CC: notm...@gmail.com
  Target Milestone: 1.0

Created attachment 171162
  --> https://bugs.kde.org/attachment.cgi?id=171162&action=edit
Issue *Contains blinking screen*

To reproduce you just need to boot into your account, then move file from
Dolphin into your desktop for the first time in that session.

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

[digikam] [Bug 489408] WAV-Files don't play anymore under Version 8.3.0.

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

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

   What|Removed |Added

  Component|Database-Files  |Preview-Engine
 OS|Other   |Linux
 CC||caulier.gil...@gmail.com

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

[Skanpage] [Bug 486771] Extremely slow UI with some driver/compositor combinations

2024-06-28 Thread Guillaume Castagnino
https://bugs.kde.org/show_bug.cgi?id=486771

Guillaume Castagnino  changed:

   What|Removed |Added

 CC||casta+...@xwing.info

--- Comment #5 from Guillaume Castagnino  ---
I can report the same issue here. I never take time to report it, but I have
the problem since the first time I use skanpage (23.04, 23.08, 24.05).
UI is damn slow for every action, but scan speed is not affected. It’s a pain
to select a scan zone, or even to save the document.

skanlite is NOT affected on the same machine.

Setup: 
- Plasma 5 under X11 (for the oldest versions)
- Plasma 6 under X11 or wayland
- Scanner : Canon LIDE 400 (PIXMA backend too, USB only)
- Computer is a recent intel-based iGPU (i5-12500)

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

[digikam] [Bug 489408] WAV-Files don't play anymore under Version 8.3.0.

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
WAV files play with the Qt6 version and QtMultimedia without any problems.
Playing WAV files tested here with the Qt5 version and QtAVPlayer under
digiKam-8.3.0 and 8.4.0 as AppImage also works here.

Maik

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

[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again

2024-06-28 Thread Kunshan Wang
https://bugs.kde.org/show_bug.cgi?id=475077

Kunshan Wang  changed:

   What|Removed |Added

 CC||wks1...@gmail.com

--- Comment #43 from Kunshan Wang  ---
Created attachment 171161
  --> https://bugs.kde.org/attachment.cgi?id=171161&action=edit
Confusion when a user sees a blog post about Overview.

The screenshot in the attachment perfectly describes my confusion.

When I upgraded to Plasma 6, I read several posts on https://planet.kde.org/
which introduces the Overview feature, and Overview differs from "Present
Windows" because it has a Desktop Bar.  But when I turn on Overview, I don't
see the Desktop Bar.  I felt very puzzled.  I thought either my system is
mis-configured or there is still a bug upstream (because it was still Plasma
6.0), and I even changed my screen edge setting from Overview to Present
Windows and back and I felt they were the same (and they do look similar
without the Desktop Bar).  And I was just about to file a bug before I found
https://bugs.kde.org/show_bug.cgi?id=485481 (which is marked as a duplicate of
this ticket) several pages in the bug list when I searched for "overview" on
product "kwin" on https://bugs.kde.org.

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

[konversation] [Bug 476580] SASL Cert does not support ecdsa certificates.

2024-06-28 Thread argonel
https://bugs.kde.org/show_bug.cgi?id=476580

argonel  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://invent.kde.org/netw
   ||ork/konversation/-/commit/3
   ||d4c92619a6a086449e14b0d28b2
   ||1af8cf7178a4
 Resolution|--- |FIXED

--- Comment #2 from argonel  ---
Git commit 3d4c92619a6a086449e14b0d28b21af8cf7178a4 by Eli MacKenzie, on behalf
of Ada Christine.
Committed on 29/06/2024 at 04:11.
Pushed by argonel into branch 'master'.

attempt to use elliptic curve private key if default RSA is null

Libera.chat changed their instructions for client certificates to use ed25519
keys. The default overload for QSslSocket::setPrivateKey() expects RSA. Attempt
to add EC private key if RSA is null.

M  +6-0src/irc/server.cpp

https://invent.kde.org/network/konversation/-/commit/3d4c92619a6a086449e14b0d28b21af8cf7178a4

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

[plasma-systemmonitor] [Bug 487752] System monitor stalls while trying to show super long "Command" popup

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

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

[kdeconnect] [Bug 488304] the notification doesn't disappear

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

--- Comment #2 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 459876] plasmashell crashed at QScopedValueRollback::QScopedValueRollback(QQmlObjectCreator*&, QQmlObjectCreator*)

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

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.

[plasmashell] [Bug 487746] Plasma shell crashes when opening status and notifications then hovering over another tray icon.

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |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.

[plasmashell] [Bug 487554] System tray widget can't be opened when on a top panel

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

--- Comment #2 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 487781] Task Manager placed on incorrect monitor when selecting primary display

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

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.

[Discover] [Bug 487791] plasma-discover: permission grant user to act as root

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

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.

[plasmashell] [Bug 487800] Plasm shell crashes after I eject Extenal SD card reader

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[plasma-systemmonitor] [Bug 484979] System Monitor has issues when running other programs.

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kmymoney] [Bug 487477] Stock price refresh not working anymore

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[plasma-systemmonitor] [Bug 486156] System Monitor will randomly crash

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[plasmashell] [Bug 487520] Plasma become unresponsive to any interactions

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

--- Comment #2 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 488022] Multiple instances of gkrellm upon reboot or logout/login

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

--- Comment #7 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 458503] Plasma crashes when unplugging screen while widget explorer is open

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

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.

[plasmashell] [Bug 418619] Plasma crashed when clicking on the 'Details' button of a cert expired dialog

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[plasmashell] [Bug 488465] Plasma crashes after reinstalling the video driver

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

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

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

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

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

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

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

[kscreenlocker] [Bug 487476] Lock Screen is Totally Broken and User Cannot Unlock Computer

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

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

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

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

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

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

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

[plasmashell] [Bug 486164] Grid layout in Widget Explorer gets jumbled when filtering

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

--- Comment #2 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 487457] Plasma (Wayland) restarts the monitor and freezes immediately after starting the computer, but windows and cursor working, rebooting does not help. In X11 session nothing fr

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

--- Comment #2 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 410856] wayland: kwin uses 100% cpu when idle

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

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

[kmymoney] [Bug 489417] New: Delete Subcategory Greyed out

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

Bug ID: 489417
   Summary: Delete Subcategory Greyed out
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: bugtracker
  Assignee: kmymoney-de...@kde.org
  Reporter: bnbu...@gmail.com
  Target Milestone: ---

Created attachment 171160
  --> https://bugs.kde.org/attachment.cgi?id=171160&action=edit
Delete sub category greyed out

Option to delete sub category greyed out. Cannot reassign because delete greyed
out.
Moved transaction to main category. Still delete greyed out.

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

[kde] [Bug 489416] New: On/Off switch for Keyboard brightness control in Brightness and Color

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

Bug ID: 489416
   Summary: On/Off switch for Keyboard brightness control in
Brightness and Color
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: fishbon...@outlook.com
  Target Milestone: ---

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

SUMMARY
In Brightness and Color there's a horizontal drag bar for keyboard brightness.
But if there's only on/off states for the keyboard brightness, why not use a
switch instead of a drag bar?

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.1.1

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 489180] plasma crashed in QtWaylandClient::QWaylandWindow::waylandScreen() when external monitor lost power

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

mitch...@ferguson.geek.nz changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||mitch...@ferguson.geek.nz

--- Comment #8 from mitch...@ferguson.geek.nz ---
Hello, I can confirm this is a bug. I get crashes in plasmashell whenever my
primary screen turns off - including when the system sleeps. New issue in 6.1.

This is particularly bad for me as my primary screen has a firmware bug causing
it to appear disconnected to the video card even when it's turned off via the
onscreen display. So when I turn my main screen off and then back on,
plasmashell crashes as it appears as if I had unplugged it and replugged it.

My stack trace is the same as the one already in the thread。

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

[krita] [Bug 480384] Crashes when right clicking "create list" in color picker

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=480384

Freya Lupen  changed:

   What|Removed |Added

 CC||vurent...@gmail.com

--- Comment #2 from Freya Lupen  ---
*** Bug 486947 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 486947] Left click and then right-click the button to "create list of colors from image" causes a crash and Krita quits abruptly.

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=486947

Freya Lupen  changed:

   What|Removed |Added

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

--- Comment #2 from Freya Lupen  ---


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

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

[kwin] [Bug 489415] kwin_wayland crash

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kwin] [Bug 489414] KWin crashes after disconnecting external display

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[bugs.kde.org] [Bug 489266] Add "SEIZURE WARNING" option to attachments

2024-06-28 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=489266

TraceyC  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from TraceyC  ---
Marking this as resolved since the request has been filed with Bugzilla

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

[krita] [Bug 487944] Time-lapse exporting error/bug

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=487944

Freya Lupen  changed:

   What|Removed |Added

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

--- Comment #1 from Freya Lupen  ---
Could you check if this bug happens on the new stable version, 5.2.3? The
"Error reinitializing filters!" should be fixed.

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

[krita] [Bug 488939] android 14. krita crashes whenever i try to import an audio file, no matter it`s size, or format.

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=488939

Freya Lupen  changed:

   What|Removed |Added

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

--- Comment #1 from Freya Lupen  ---
This bug should be fixed on the new stable version, 5.2.3, could you check
that?

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

2024-06-28 Thread Thomas Carmichael
https://bugs.kde.org/show_bug.cgi?id=484323

Thomas Carmichael  changed:

   What|Removed |Added

 CC||carmanau...@gmail.com

--- Comment #35 from Thomas Carmichael  ---
I've been able to reliably reproduce this so far by the following:

STEPS TO REPRODUCE
1. Lock the screen
2. Turn off the monitor directly via the power button (for me it's the monitor
OSD with a power action)
3. Turn the monitor back on

>From this point forward, while the screen is locked there will be high CPU
load.

For me, restarting "kwin_x11" via systemd ("systemctl --user restart
plasma-kwin_x11.service") temporarily fixes the issue until the screen ends up
turned off again.

Operating System: EndeavourOS 
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.6-arch1-1 (64-bit)
Graphics Platform: X11
Graphics Processor: AMD Radeon RX 6400

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

[kwin] [Bug 489415] New: kwin_wayland crash

2024-06-28 Thread Kevin Schier
https://bugs.kde.org/show_bug.cgi?id=489415

Bug ID: 489415
   Summary: kwin_wayland crash
Classification: Plasma
   Product: kwin
   Version: 6.1.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: schierke...@gmail.com
  Target Milestone: ---

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

SUMMARY
kwin_wayland crashes through various means. 

STEPS TO REPRODUCE
1. Open debug console with "qdbus6 org.kde.KWin /KWin
org.kde.KWin.showDebugConsole". This also happens randomly when using the
taskswitcher and also seemingly at random

OBSERVED RESULT
Entire desktop dies. Restart afterwards some of the time

EXPECTED RESULT
A working desktop

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 15,6 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: ECT

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

[kwin] [Bug 489414] New: KWin crashes after disconnecting external display

2024-06-28 Thread Jonah Brüchert
https://bugs.kde.org/show_bug.cgi?id=489414

Bug ID: 489414
   Summary: KWin crashes after disconnecting external display
Classification: Plasma
   Product: kwin
   Version: 6.1.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: j...@kaidan.im
CC: davids.paskev...@gmail.com
  Target Milestone: ---

SUMMARY
The device is configured to go to sleep once no displays are connected.
The crash happens when the device is woken back up, possibly connected to a new
external display.

The bug is not always reproducible.

This crash didn't happen on my own device, I'm reporting for someone else.

The backtrace is the same as the following sentry report
https://crash-reports.kde.org/organizations/kde/issues/36638/events/ee240964d5b54f0e8371a45b3dae8499/
(It's required to show the Full Stack Trace, as sentry otherwise filters the
relevant parts)

Possibly Output *m_moveResizeOutput in window.h should be stored in a QPointer,
as it seems to be reference counted and not guaranteed to still exist. A check
for whether it is null already exists, but it wouldn't catch a dangling
pointer.

I don't have a development setup for Plasma right now to verify this.

STEPS TO REPRODUCE
1. have laptop go to sleep automatically
2. Disconnect laptop from docking station
3. Wake up laptop connected to other display

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1

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

[kdenlive] [Bug 489412] Problemas visuales de la exportacion - Export visual problems

2024-06-28 Thread Bernd
https://bugs.kde.org/show_bug.cgi?id=489412

Bernd  changed:

   What|Removed |Added

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

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

[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep

2024-06-28 Thread tess
https://bugs.kde.org/show_bug.cgi?id=448866

--- Comment #29 from tess  ---
happening on 555.58 as well

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

[kdenlive] [Bug 489412] Problemas visuales de la exportacion - Export visual problems

2024-06-28 Thread Bernd
https://bugs.kde.org/show_bug.cgi?id=489412

Bernd  changed:

   What|Removed |Added

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

--- Comment #2 from Bernd  ---


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

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

[kdenlive] [Bug 488433] Rendering Time is no longer accurate

2024-06-28 Thread Bernd
https://bugs.kde.org/show_bug.cgi?id=488433

Bernd  changed:

   What|Removed |Added

 CC||byrongamer...@gmail.com

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

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

[kdenlive] [Bug 489412] Problemas visuales de la exportacion - Export visual problems

2024-06-28 Thread Bernd
https://bugs.kde.org/show_bug.cgi?id=489412

Bernd  changed:

   What|Removed |Added

 CC||bern...@yahoo.com
Summary|Problemas visuales de la|Problemas visuales de la
   |exportacion |exportacion - Export visual
   ||problems

--- Comment #1 from Bernd  ---
(In reply to Byron from comment #0)
> Created attachment 171156 [details]
> Imagen de prueba sobre el problema visual de la exportacion
> 
> Al momento de procesar el video, la barra de carga y el tiempo de proceso,
> estan funcionando mal, pero almenos no afecta enel procesamiento ya que al
> final, se termina de procesar bien. Lo malo es el problema de visualizar el
> tiempo del procesamiento de video.

Next time, please post in English, even if you have to use Google translate
(like I did):

Test image on the visual export problem

When processing the video, the loading bar and the processing time are working
poorly, but at least it does not affect the processing since in the end, it
finishes processing well. The bad thing is the problem of displaying the video
processing time.

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

[plasmashell] [Bug 489413] New: The "Add Widget…" button on an empty panel has a rather unhelpful tooltip menu in Panel Configuration mode

2024-06-28 Thread cwo
https://bugs.kde.org/show_bug.cgi?id=489413

Bug ID: 489413
   Summary: The "Add Widget…" button on an empty panel has a
rather unhelpful tooltip menu in Panel Configuration
mode
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: christoph.w...@gmx.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

(Originally mentioned as an aside in #488792, filing as a new bug so it doesn't
get lost)

SUMMARY

Empty panels permanently display an "Add widget…" button that opens the Widget
Explorer, inviting users to make use of the empty panel they added. If the user
is in Panel Configuration mode and hovers the mouse over this button, a tooltip
menu opens as if the button were a regular widget. This tooltip, however, is
completely useless. It only contains a title field and an entry for "Show
Alternatives". The title field is empty. "Show Alternatives…", reasonably
enough, doesn't do anything when clicked - there's really no alternative to an
"Add widgets…" button. All together, this popup contains zero information and
nothing for the user to meaningfully interact with.

STEPS TO REPRODUCE
1. Right-click the desktop, "Enter Edit Mode…", Add Panel > Empty Panel
2. Right-click the new panel, "Show panel configuration"
3. Hover the mouse over the "Add widgets…" button on the empty panel.

OBSERVED RESULT

A useless popup.

EXPECTED RESULT

No popup.

(Alternatively, a popup that contains only the title of the button, "Add
Widget…", instead of the empty title area. This has a rather niche use case: on
a vertical panel, the "Add widget…" text is missing. A user unsure about what
the button does, but who knows about the tooltips in Panel Configuration mode,
or happens to be in that mode, might use this to figure out what the button
does. My intuition is that this is too marginal to justify keeping the tooltip,
but I don't have strong opinions on this)

SOFTWARE/OS VERSIONS

current neon dev
KDE Plasma Version: 6.1.80
KDE Frameworks Version: 6.4.80
Qt Version: 6.7.0

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

[plasmashell] [Bug 489259] Spamming Meta+V causes Plasma to exit with a Wayland protocol error (error 3: no xdg_popup parent surface has been specified)

2024-06-28 Thread Kevin Schier
https://bugs.kde.org/show_bug.cgi?id=489259

--- Comment #13 from Kevin Schier  ---
Created attachment 171157
  --> https://bugs.kde.org/attachment.cgi?id=171157&action=edit
This is the core dump I get from the clipboard

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

[plasmashell] [Bug 489411] Plasmashell crashes, possibly after closing a window with children windows

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kwin] [Bug 488941] Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled

2024-06-28 Thread kryptokatalyst
https://bugs.kde.org/show_bug.cgi?id=488941

--- Comment #7 from kryptokatalyst  ---
Also, same behavior as submitter:

1. Backup .config/kwinoutputconfig.json
2. Enable HDR in Wayland session (nothing else) everything works fine during
that session.  
3. Reboot or re-log and I get:

w/o nvidia  in initramfs & nvidia_drm.modeset=1 and nvidia_drm.fbdev=1 
> Black screen w/white cursor

w/nvidia  in initramfs & nvidia_drm.modeset=1 and nvidia_drm.fbdev=1
> No signal to display

4. Login to X11 session and restore .config/kwinoutputconfig.json
5. Reboot/re-log into Wayland session; everything fine again (HDR off)

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

[plasmashell] [Bug 489259] Spamming Meta+V causes Plasma to exit with a Wayland protocol error (error 3: no xdg_popup parent surface has been specified)

2024-06-28 Thread Kevin Schier
https://bugs.kde.org/show_bug.cgi?id=489259

Kevin Schier  changed:

   What|Removed |Added

 CC||schierke...@gmail.com

--- Comment #12 from Kevin Schier  ---
I also have this issue. I also get crashes when opening the debug console via
"qdbus6 org.kde.KWin /KWin org.kde.KWin.showDebugConsole
" with the same error "QDBusError("org.freedesktop.DBus.Error.UnknownObject",
"No such object path". General instability and freezes after upgrading to 6.1.1

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

[kscreenlocker] [Bug 466178] kscreenlocker crash recovery advice doesn't make sense when there are no VTs

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

--- Comment #3 from bluescreenaven...@gmail.com ---
https://github.com/systemd/systemd/pull/29542 is merged, which might be
relevant to this
This could allow new instructions to where they are to press Ctrl+Alt+Shift+Esc
and then log in with a new session (would have to be like Weston or something
because you can't have two systemd handled sessions) and then run the command
with that

...that is once the patch is in in sddm

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

[kwin] [Bug 488941] Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled

2024-06-28 Thread kryptokatalyst
https://bugs.kde.org/show_bug.cgi?id=488941

kryptokatalyst  changed:

   What|Removed |Added

 CC||kryptokatal...@gmail.com

--- Comment #6 from kryptokatalyst  ---
I also starting having this on Arch/Nvidia 550 when KDE updated to 6.1 in the
`extra` repo.

Relevant `journalctl` output:

Repeated:

>Jun 20 17:03:07 gogeta kwin_wayland[2604]: kwin_scene_opengl: 0x502: 
>GL_INVALID_OPERATION error generated.  and  are incompatible
>Jun 20 17:03:07 gogeta kwin_wayland[2604]: kwin_scene_opengl: Invalid 
>framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"

Followed by single:

> Jun 20 17:03:07 gogeta kwin_wayland[2604]: kwin_wayland_drm: Checking test 
> buffer failed!
> Jun 20 17:03:07 gogeta kwin_wayland[2604]: kwin_core: Applying output config 
> failed!

Issue exists under every permutation of [NVIDIA
DRM](https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting).

>OS: Arch Linux x86_64
>Host: X570S I AORUS PRO AX (-CF)
>Kernel: Linux 6.9.6-arch1-1
>Uptime: 15 hours, 28 mins
>Packages: 970 (pacman)
>Shell: bash 5.2.26
>Display (AW3225QF): 3840x2160 @ 120Hz (HDMI 2.1)
>DE: KDE Plasma 6.1.0
>WM: KWin (X11)
>WM Theme: Breeze
>Theme: Breeze (Dark) [QT], Breeze-Dark [GTK2], Breeze [GTK3/4]
>Icons: breeze-dark [QT], breeze-dark [GTK2/3/4]
>Font: Noto Sans (10pt) [QT], Noto Sans (10pt) [GTK2/3/4]
>Cursor: breeze (24px)
>Terminal: yakuake 24.05.1
>CPU: AMD Ryzen 5 5600 (12) @ 3.50 GHz
>GPU: NVIDIA GeForce RTX 4070 SUPER [Discrete]

Have just been leaving HDR off until it's resolved, and X11 for gaming until
official NVIDIA driver update for explicit sync.

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

[PlasmaTube] [Bug 475967] Volume control in the video player

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

louisv...@gmail.com changed:

   What|Removed |Added

 CC||louisv...@gmail.com

--- Comment #1 from louisv...@gmail.com ---
It also uses the same volume as mpv which makes it extra annoying.

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

[PlasmaTube] [Bug 485810] Videos played in a detached window

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

louisv...@gmail.com changed:

   What|Removed |Added

 CC||louisv...@gmail.com

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

[plasmashell] [Bug 489411] Plasmashell crashes, possibly after closing a window with children windows

2024-06-28 Thread Jonah Brüchert
https://bugs.kde.org/show_bug.cgi?id=489411

Jonah Brüchert  changed:

   What|Removed |Added

 CC||davids.paskev...@gmail.com

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

[kdenlive] [Bug 489412] New: Problemas visuales de la exportacion

2024-06-28 Thread Byron
https://bugs.kde.org/show_bug.cgi?id=489412

Bug ID: 489412
   Summary: Problemas visuales de la exportacion
Classification: Applications
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: byrongamer...@gmail.com
  Target Milestone: ---

Created attachment 171156
  --> https://bugs.kde.org/attachment.cgi?id=171156&action=edit
Imagen de prueba sobre el problema visual de la exportacion

Al momento de procesar el video, la barra de carga y el tiempo de proceso,
estan funcionando mal, pero almenos no afecta enel procesamiento ya que al
final, se termina de procesar bien. Lo malo es el problema de visualizar el
tiempo del procesamiento de video.

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

[kdenlive] [Bug 487045] rendering takes forever even if I only want to render a 360p preview

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

--- Comment #8 from die4ever2...@gmail.com ---
Rendering just the audio track also takes longer than I would expect. I just
rendered a 1h55m 4k 60fps video (video track and audio track) in 10 hours, then
I wanted to mess with the audio levels so I figured I would just render audio
and then use ffmpeg to merge them. 

But the audio rendering took 1h22m50s, which is definitely an improvement but I
would've expected better than 2x rendering speed compared to playback speed for
just audio.

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

[plasmashell] [Bug 489411] New: Plasmashell crashes, possibly after closing a window with children windows

2024-06-28 Thread Jonah Brüchert
https://bugs.kde.org/show_bug.cgi?id=489411

Bug ID: 489411
   Summary: Plasmashell crashes, possibly after closing a window
with children windows
Classification: Plasma
   Product: plasmashell
   Version: 6.1.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Window List
  Assignee: plasma-b...@kde.org
  Reporter: j...@kaidan.im
CC: uhh...@gmail.com
  Target Milestone: 1.0

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

First of all, I didn't experience this bug myself, I just saw it on someone
elses computer and debugged it somewhat.

SUMMARY
Plasmashell crashes

The backtrace is the same as this sentry report:
https://crash-reports.kde.org/organizations/kde/issues/38215/?project=9&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=90d&stream_index=9

The backtrace is attached below for reference.


My current theory is this:
A window that still has children windows is being closed.

The function in which this crashes is the lambda connected to
&PlasmaWindow::parentWindowChanged in waylandtasksmodel.cpp:635.

The lambda is only invoked, because QObject::destroyed is connected to
&PlasmaWindow::parentWindowChanged in waylandtasksmodel:320

Qt does a direct connection here, so then parentWindowChanged is invoked as
part of the destructor of PlasmaWindow, which is probably not what's wanted
here. Possibly a QueuedConnection would fix this.

My theory is that the window that is being deleted is accessed by the code
called in the result of the destructor.

I don't have a proper setup to test my theory right now.


STEPS TO REPRODUCE
Currently unknown


SOFTWARE/OS VERSIONS
KDE Plasma Version:  6.1.1

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

[dolphin] [Bug 488154] Addition of a dedicated Tags Panel

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

--- Comment #6 from m1vri...@duck.com ---
It is also worthwhile in the filter view to be able to switch between filtering
only at the current directory level or also searching subdirectories.

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

[konsole] [Bug 482628] Allow disabling toolBar accelerator

2024-06-28 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=482628

Nick  changed:

   What|Removed |Added

 CC||juszcz...@gmail.com

--- Comment #11 from Nick  ---
FWIW, I just recently ran into this on opensuse tumbleweed, and was able to
work around this by hiding the session toolbar which contains the Find
operation.

Settings > Toolbars Shown > deselect Session Toolbar

This was particularly annoying when using SSH + Emacs, which makes heavy use of
pretty much all of the modifier keys.

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

[kwin] [Bug 488941] Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled

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

davidgill...@gmail.com changed:

   What|Removed |Added

 CC||davidgill...@gmail.com

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

[frameworks-baloo] [Bug 489406] Baloo doesn't automatically index multimedia files' metadata

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

--- Comment #5 from malikt...@gmail.com ---
> Also worth checking whether you have content indexing enabled...
Setting "only basic indexing=false" in baloofilerc now causes it to index
automatically as I enable columns in Dolphin's detail view mode, which is what
I expected to have happen by default.

> A couple of tricks here, you can watch what Baloo is content indexing with:
> $ balooctl6 monitor
> and you'll see a stream of files as they are indexed...
> 
> You can also prod Baloo to go and check for new/changed files with:
> $ balooctl6 check
You can see I did these in my original bug report. balooctl6 monitor did not
return anything even when I manually indexed a file with balooctl6 index.
balooctl6 check did nothing.

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

[kwin] [Bug 489334] whole system crashes after disabling window snapping

2024-06-28 Thread sonicbluesky
https://bugs.kde.org/show_bug.cgi?id=489334

--- Comment #2 from sonicbluesky  ---
yes i rebooted

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

[kwin] [Bug 489410] kwin_wayland crash

2024-06-28 Thread kinghat
https://bugs.kde.org/show_bug.cgi?id=489410

--- Comment #1 from kinghat  ---
Created attachment 171154
  --> https://bugs.kde.org/attachment.cgi?id=171154&action=edit
krash report

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

[Qt/KDE Flatpak Runtime] [Bug 409300] KDE Platform flatpak runtime is missing any theme's sounds

2024-06-28 Thread skierpage
https://bugs.kde.org/show_bug.cgi?id=409300

skierpage  changed:

   What|Removed |Added

Summary|KDE Platform flatpak|KDE Platform flatpak
   |runtime is missing the  |runtime is missing any
   |Oxygen theme's sounds   |theme's sounds

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

[kwin] [Bug 489410] New: kwin_wayland crash

2024-06-28 Thread kinghat
https://bugs.kde.org/show_bug.cgi?id=489410

Bug ID: 489410
   Summary: kwin_wayland crash
Classification: Plasma
   Product: kwin
   Version: 6.1.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: madl...@gmail.com
  Target Milestone: ---

SUMMARY
have had plasma crash about every day since either 6.1 or 6.1.1. i dont know
what it is but the system is also really sluggish. sometimes its fine after
reboot and then it will be sluggish after screen was locked for a while or from
suspend. ive also had the firefox flatpak freeze and crash a few times as well. 

the last couple plasma crashes were when using discord flatpak or when i was in
the overview. i dont think the applications are responsible but has something
to do with the system being extremely sluggish. i have attached the krash
report and was told it might be useful even though the reporter said it wasnt.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.6-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION

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

[frameworks-baloo] [Bug 489406] Baloo doesn't automatically index multimedia files' metadata

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

--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to malikth32 from comment #2)
> ... then running balooshow6 -x,
> returns "No index information found". So this appears to be an indexing
> problem ...
A couple of tricks here, you can watch what Baloo is content indexing with:
$ balooctl6 monitor
and you'll see a stream of files as they are indexed...

You can also prod Baloo to go and check for new/changed files with:
$ balooctl6 check

> ... I'm a little confused though, because Dolphin still shows album art
> properly. Is that processed outside of Baloo? ...
Good question, no I don't think Baloo's involved here... It could be a separate
"thumbnailing" process.

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

[krita] [Bug 488748] Touch docker doesn't work in Android. It shows just white blank.

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=488748

Freya Lupen  changed:

   What|Removed |Added

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

--- Comment #1 from Freya Lupen  ---


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

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

[kate] [Bug 481626] Sessions UI seems extremely confusing

2024-06-28 Thread Lassi Väätämöinen
https://bugs.kde.org/show_bug.cgi?id=481626

--- Comment #10 from Lassi Väätämöinen  ---
Created attachment 171153
  --> https://bugs.kde.org/attachment.cgi?id=171153&action=edit
Filesystem pane bookmarks

(In reply to Ellie from comment #7)
> I don't quite understand why the folders can't just be separate. I attached
> an image to show how to do that for the "Open Recent" menu. 

I think that can be quite feasible. I don't know the general Kate design
principles, and how would this impact general usability. Or whehter this having
folders listed separately is generally useful.

(In reply to Ellie from comment #8)
> For example, I  always open the same 2-3 folders on most days. If I just had 
> a quick access
> to them, I wouldn't ever need to use sessions.

Ok, so sounds like you would be using Recent folders mostly just to get back to
this fixed set of folders daily. Something like "bookmarks" in a web browser.

In fact, the Filesystem browser in Kate has bookmarks, and those are global
across windows, so you could just bookmark the most used folders, open separate
windows, open a bookmark in each window. And you also can get back to the "good
known location" bookmar, after wandering in the non-trivial folders.

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

[krita] [Bug 476690] touch docker is blank

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=476690

Freya Lupen  changed:

   What|Removed |Added

 CC||kang...@naver.com

--- Comment #8 from Freya Lupen  ---
*** Bug 488748 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 481626] Sessions UI seems extremely confusing

2024-06-28 Thread Ellie
https://bugs.kde.org/show_bug.cgi?id=481626

--- Comment #9 from Ellie  ---
> I guess it's a bit philosophical what a user considers a session. As you 
> mentioned earlier, you open 4 windows with different "project" in each 
> window, but I understand they are seeminly related, hence each project and 
> window can be considered belonging to your session. 

For what it's worth, it's not that I protest to either concept of a session. I
have no strong personal opinion on what's more counter-intuitive. However, when
closing all kate windows this doesn't seem to work well with the sessions as
they work now. So there seems to be a strong practical reason to have them per
window. However, you would probably best ask heavier user of the sessions to
figure out what they think about that. I realize I'm not the right person for
trustworthy sessions advice, since I eventually decided not to use them.

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

[frameworks-baloo] [Bug 489406] Baloo doesn't automatically index multimedia files' metadata

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

--- Comment #3 from tagwer...@innerjoin.org ---
Also worth checking whether you have content indexing enabled...

These are "embedded" properties, part of the file. Baloo will only open the
file to find and index them if it has content indexing enabled. I think that a
"balooctl6 index ..." always indexes the content.

... I should double check that

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

[plasmashell] [Bug 487959] Brightness no longer working since 6.0.90

2024-06-28 Thread Nico
https://bugs.kde.org/show_bug.cgi?id=487959

Nico  changed:

   What|Removed |Added

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

--- Comment #8 from Nico  ---
Oh wait, it worked before but not it's broken again. It now shows the correct
percentage value from the slider but it doesn't control the brightness

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

[plasmashell] [Bug 487959] Brightness no longer working since 6.0.90

2024-06-28 Thread Nico
https://bugs.kde.org/show_bug.cgi?id=487959

Nico  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Nico  ---
Fixed in 6.1.1

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

[dolphin] [Bug 489409] New: "Remember password" checkbox state isn't configurable

2024-06-28 Thread Ellie
https://bugs.kde.org/show_bug.cgi?id=489409

Bug ID: 489409
   Summary: "Remember password" checkbox state isn't configurable
Classification: Applications
   Product: dolphin
   Version: 24.05.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: e...@horse64.org
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

The "Remember password" checkbox state when mounting any encrypted device
should perhaps either reflect last used state, or be configurable, for security
reasons. It can be unsafe in some environments to remember the password for
removable encrypted devices, so this prompt showing up and then always having
"Remember password" pre-checked with no way of stopping that can be a risk when
handling such removable devices a lot. Sadly, neither does this checkbox seem
to reflect what I last used nor can I find anything in the dolphin options to
change it not to be checked by default as to avoid accidentally using it.

Is there a way to disable this mechanism entirely? Maybe if I uninstall KDE
Wallet for now?

STEPS TO REPRODUCE

1.  Access encrypted removable device in Dolphin
2. "Password" dialog pops up, "Remember password" is pre-checked

OBSERVED RESULT

I can't find a way for not making "Remember password" pre-checked every time.

EXPECTED RESULT

There's a way to disable this default state. E.g. if it remembered what I last
used, that would already be enough since then I just need to be careful the
first time and then it'll be fixed for follow-up uses.

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Slowroll
(available in About System)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[xdg-desktop-portal-kde] [Bug 473653] OBS Studio - Only shows a Black Screen when trying to record either Monitors or App Windows under KDE Plasma Wayland on my Intel PC

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

mpalys7...@gmail.com changed:

   What|Removed |Added

 CC||mpalys7...@gmail.com

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

[xdg-desktop-portal-kde] [Bug 485283] blank screen in obs studio

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

mpalys7...@gmail.com changed:

   What|Removed |Added

 CC||mpalys7...@gmail.com

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

[frameworks-baloo] [Bug 489406] Baloo doesn't automatically index multimedia files' metadata

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

--- Comment #2 from malikt...@gmail.com ---
Viewing the properties of a file in Dolphin, then running balooshow6 -x,
returns "No index information found". So this appears to be an indexing
problem.

After indexing it manually with balooctl6 index, it returns metadata.

...I'm a little confused though, because Dolphin still shows album art
properly. Is that processed outside of Baloo?

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

[kdenlive] [Bug 489210] render time says remaining time 0:00:00 for hours while it actually finishes rendering

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

--- Comment #2 from die4ever2...@gmail.com ---
I also often see the fps showing a negative number

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

[krita] [Bug 488800] Clearing scratchpad while brush is lagging crashes Krita

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=488800

Freya Lupen  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||penguinflyer2...@gmail.com
 Ever confirmed|0   |1

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

[krita] [Bug 474691] UI: glitch in layout of the "resize" tab contents in the "export advanced" dialog

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=474691

Freya Lupen  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||penguinflyer2...@gmail.com

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

[krita] [Bug 468202] Krita on Android freezes after creating a new document or opening a pre-existing one

2024-06-28 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=468202

Freya Lupen  changed:

   What|Removed |Added

 CC||penguinflyer2...@gmail.com

--- Comment #6 from Freya Lupen  ---
Though seemingly similar, I believe the issue on 5.2.3 is a completely
different bug (reported as bug 488606).
This bug report involves Krita becoming completely unresponsive after having
been installed for some time, while the other bug involves Krita becoming
partially unresponsive regardless of how long it's been installed.

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

[frameworks-baloo] [Bug 489406] Baloo doesn't automatically index multimedia files' metadata

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

tagwer...@innerjoin.org changed:

   What|Removed |Added

 CC||tagwer...@innerjoin.org

--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to malikth32 from comment #0)
> ... Baloo doesn't automatically index metadata specific to multimedia files by
> default, such as a music file's Duration or Artist...
What happens when ...

> 1. Create or obtain an audio or video file, then go to its directory in
> Dolphin and view its Properties (right-click > Properties).
... and then check to see what Baloo has indexed with a:
 $ balooshow6 -x your-multimedia-file.mp3

Is the issue with indexing or Dolphin picking up the indexed metadata?

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

[kate] [Bug 481626] Sessions UI seems extremely confusing

2024-06-28 Thread Ellie
https://bugs.kde.org/show_bug.cgi?id=481626

--- Comment #8 from Ellie  ---
Sorry, I forgot to actually answer: the use case of having recent folders
separate is for people who want to avoid the sessions UI. For example, I always
open the same 2-3 folders on most days. If I just had a quick access to them, I
wouldn't ever need to use sessions. This would make any confusion or complexity
with the sessions less impactful, since while it wouldn't fix anything about
the sessions, it would allow users to get by better without them.

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

[kate] [Bug 481626] Sessions UI seems extremely confusing

2024-06-28 Thread Ellie
https://bugs.kde.org/show_bug.cgi?id=481626

--- Comment #7 from Ellie  ---
Created attachment 171152
  --> https://bugs.kde.org/attachment.cgi?id=171152&action=edit
Concept of separate recent folders in "Open Recent"

> So as such recent documents here work as they are meant to: they contain the
recent locations you worked in. 

I don't quite understand why the folders can't just be separate. I attached an
image to show how to do that for the "Open Recent" menu. As for the "Welcome"
screen, I think best would be two tabs for "Documents" vs "Folders" added above
the top files list.

The problem is that the files flood the history list to the point that it's not
possible to get back to old folders using it.

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

[krusader] [Bug 476194] sync only changed files no more possible

2024-06-28 Thread Alexei Pastor
https://bugs.kde.org/show_bug.cgi?id=476194

Alexei Pastor  changed:

   What|Removed |Added

 CC||avpas...@hotmail.com

--- Comment #2 from Alexei Pastor  ---
I have the same bug. It is impossible to synchronize two folders in asymmetric
mode. It just mark all "different" files by "!=", but it schould to mark them
by "<-".

ADDITIONAL INFORMATION:
Operating System: Debian 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-21-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-3470 CPU @ 3.20GHz
Memory: 7,7 GiB of RAM
Graphics Processor: NVE7
Manufacturer: Gigabyte Technology Co., Ltd.

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

[digikam] [Bug 489408] New: WAV-Files don't play anymore under Version 8.3.0.

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

Bug ID: 489408
   Summary: WAV-Files don't play anymore under Version 8.3.0.
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Database-Files
  Assignee: digikam-bugs-n...@kde.org
  Reporter: br...@ekmain.de
  Target Milestone: ---

Hello,

Yesterday I have installed Version 8.3.0 and now the audio-Files (WAV) don't
play anymore. Under 8.2.0 this was okay.  Please check it.

Best regards,
Erich

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

[kate] [Bug 481626] Sessions UI seems extremely confusing

2024-06-28 Thread Lassi Väätämöinen
https://bugs.kde.org/show_bug.cgi?id=481626

--- Comment #6 from Lassi Väätämöinen  ---
(In reply to Ellie from comment #5)
> You're right, most likely I closed the windows shortly after each other.
> This wouldn't be a potential pitfall however if sessions by default were per
> window. I don't think making them global is very intuitive, given most other
> actions are per window.
> 

I guess it's a bit philosophical what a user considers a session. As you
mentioned earlier, you open 4 windows with different "project" in each window,
but I understand they are seeminly related, hence each project and window can
be considered belonging to your session. 


> "File" > "Open Recent" not separating folders and files into separate lists,
> which means if any non-trivial folder is opened and used for a while, the
> recent list will only include files and not folders.

I have to say I haven't ever tried using Recents list of any application too
extensively, but for such uses as getting back to - yes to a recent document.
So as such recent documents here work as they are meant to: they contain the
recent locations you worked in. 

> It doesn't seem to be  possible to quickly get back to your last folder in a 
> non-annoying way,
> without sessions. The welcome tab's "Recent Documents and Projects" seems to
> suffer from the same problem. If that worked better, sessions would be less
> required for the average user.

I can't quite grasp your workflow here, and how you are using Recents in
general. Like, you would lke to get back to some folder you worked in some
minutes ago, after browsing through other files and folders ("non-trivial
folders"), or when you get back to your session the next  day to set up the
session again? Or what is your primary goal of using Recents?

If it's just a matter of getting back to a certain folder after a while, the
Documents pane shows your currently open folders and and documents in a
particular window, and the documents are hilighted based on "recency".

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

[okular] [Bug 470438] Open new files in tab does not work in flatpak verison of Okular 23.04.1

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

kwvanderli...@gmail.com changed:

   What|Removed |Added

 CC||kwvanderli...@gmail.com

--- Comment #1 from kwvanderli...@gmail.com ---
Did some digging on this as I encountered the same problem on Linux Mint with
Okular 24.05.1. I'm not an expert with the tech involved, but the issue seems
to be a combo of collisions between D-Bus service names and lack of permissions
on the flatpak itself.

For flatpak permissions, okular needs to have access to the session bus since
it needs to discover the other okular services. But the flatpak does not have
this permission set by default and so the user has to enable it explicitly.

For the D-Bus service name, okular includes the PID, which normally results in
separate a D-Bus service for each okular process. But under flatpak, the PID is
always the same due to running under a separate PID namespace (e.g., I always
see a PID of 2). So when okular is already running, and we try to open a new
document from the file explorer, the new okular process will have the same PID
and D-Bus service name as the existing process. So even if the new process
could discover the existing process service, it will think it just discovered
itself and won't send the new paths over to the existing process.

As a workaround, here's what I did to get the flatpak to open docs in new tabs
instead of new windows:
1. Add the `socket=session-bus` permission, e.g., through flatseal. This is
generally not recommended by flatpak, but is required for service discovery.
2. Enable PID sharing with the top-level namespace, which will give each okular
process a distinct PID. Instead of `flatpak run org.kde.okular`, use `flatpak
--parent-pid=1 --parent-share-pids run org.kde.okular`.

I think the ideal (from a flatpak perspective) would be for okular to use one
d-bus service with a consistent name rather than having a unique service
per-process. This way the flatpak would only need permission for that
particular service instead of the entire session bus. It would also mean there
would be no issue with PID collisions, so those would not have to be shared
with the parent namespace.

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

[lokalize] [Bug 489407] New: Greek Acute Input Error

2024-06-28 Thread Dimitrys
https://bugs.kde.org/show_bug.cgi?id=489407

Bug ID: 489407
   Summary: Greek Acute Input Error
Classification: Applications
   Product: lokalize
   Version: 24.05.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sdepi...@gmail.com
  Reporter: demetresmeliates+...@gmail.com
CC: aa...@kde.org, sha...@ukr.net
  Target Milestone: ---

Created attachment 171151
  --> https://bugs.kde.org/attachment.cgi?id=171151&action=edit
1. This line was already tranlated, I just went to do a minor fix. 2.
Simuntanusly I was pressing the Acute simbol and it din't input the acute at
all.

SUMMARY
Greek acute ("´") does not apply in any Greek vowel and/or at all.

STEPS TO REPRODUCE
1. Install Greek Locale
2. Type a Greek vowel by simultaneously pressing the ";" button.

OBSERVED RESULT
It will not apply the acute in the vowel. It will look like that 
Button = Κουμπι

EXPECTED RESULT
It should appear like this:
Button = Κουμπί

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

ADDITIONAL INFORMATION
Acute is simply used to say a vowel louder in a word and it is a basic
grammatical rule.

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

  1   2   3   4   >