date:20250406

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

b...@mogwai.be changed:

   What|Removed |Added

 CC||bebe...@gmail.com

--- Comment #6 from b...@mogwai.be ---
*** Bug 502468 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 461586] Uninformative notification when I try to set a weak password to wi-fi connection

2025-04-06 Thread Abdullah

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

Abdullah  changed:

   What|Removed |Added

 OS|Linux   |macOS
  Component|kcm_networkmanagement   |kcm_snap
 CC||g7aag...@gmail.com

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

[kwin] [Bug 502481] New: Magnifier effect doesn't follow pen tablet stylus

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

Bug ID: 502481
   Summary: Magnifier effect doesn't follow pen tablet stylus
Classification: Plasma
   Product: kwin
   Version: 6.2.5
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: cyber+...@sysrq.in
  Target Milestone: ---

SUMMARY
Magnifier only follows mouse movement, not pen tablet movement. My graphics
tablet is Huion 420 using standard Linux driver, hid_uclogic.

STEPS TO REPRODUCE
1. Enable Magnifier
2. Move the cursor using a stylus

OBSERVED RESULT
Magnified area doesn't move.

EXPECTED RESULT
Magnified area moves with the cursor.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.14.0-gentoo (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD FX-8320E Eight-Core Processor
Memory: 11.6 ГиБ of RAM
Graphics Processor: NVD9

ADDITIONAL INFORMATION

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

[kwin] [Bug 502481] Magnifier effect doesn't follow pen tablet stylus

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

Anna  changed:

   What|Removed |Added

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

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

[kwin] [Bug 492626] Zoom not following drawing tablet

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

Anna  changed:

   What|Removed |Added

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

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

[kwin] [Bug 492626] Zoom not following drawing tablet

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

Anna  changed:

   What|Removed |Added

 CC||cyber+...@sysrq.in

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

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

2025-04-06 Thread Jarrard

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

Jarrard  changed:

   What|Removed |Added

 CC||jarr...@proton.me

--- Comment #102 from Jarrard  ---
I just had this happen I think. Kwin_wayland was eating 46GB of shared memory,
system was really feeling it too, closed the process and it restarted with
normal usage (330mb or so).  Bit annoying, am using 4090 with open-nvidia
drivers 6.14 kernel (cachyos)

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

[krita] [Bug 502484] New: Layer Merging

2025-04-06 Thread Josiah Zimmerle

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

Bug ID: 502484
   Summary: Layer Merging
Classification: Applications
   Product: krita
   Version: 5.2.9
  Platform: Compiled Sources
OS: All
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: layer styles
  Assignee: krita-bugs-n...@kde.org
  Reporter: zimmerlejos...@gmail.com
  Target Milestone: ---

After going out of the krita tab ( I didn't close it just went to a different
tab) I came back and all of my layers were merged onto "root merged". This is a
big problem

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

[plasma-browser-integration] [Bug 501991] Job progress notification from browser via plasma-browser-integration freezes and OOMs plasmashell

2025-04-06 Thread Fushan Wen

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

--- Comment #6 from Fushan Wen  ---
Git commit 6873a38d94b389118dc6b896473d6a10824dbef3 by Fushan Wen.
Committed on 06/04/2025 at 11:58.
Pushed by fusionfuture into branch 'master'.

appiumtests: add test for job notification

1. A job is created without a total amount of bytes to test bug 502001.
2. Elements in a job notification are examined.
3. Update the job progress, and the notification should report progress,
   speed and remaining time.
4. When a job is complete, "Job Finished" and the destination url should
   show up.

M  +42   -2appiumtests/applets/notificationstest.py
A  +0-0appiumtests/applets/notificationstest/__init__.py
A  +64   -0appiumtests/applets/notificationstest/jobnotification.py
A  +55   -0   
appiumtests/applets/notificationstest/jobnotificationinterface.py
M  +2-0applets/notifications/package/contents/ui/components/JobItem.qml
M  +2-0   
applets/notifications/package/contents/ui/components/SpeedChart.qml

https://invent.kde.org/plasma/plasma-workspace/-/commit/6873a38d94b389118dc6b896473d6a10824dbef3

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

[kmymoney] [Bug 502306] Add option to display both the amount and its percentage on charts

2025-04-06 Thread Thomas Baumgart

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

Thomas Baumgart  changed:

   What|Removed |Added

   Severity|normal  |wishlist
Summary|Inclusion of Opening|Add option to display both
   |Balances in Net Worth   |the amount and its
   |Report on a Specific Date   |percentage on charts

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

[krita] [Bug 502157] Krita Next Nightlies SAFE ASSERT Internal Errors and Crash when using Tablet

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

Freya Lupen  changed:

   What|Removed |Added

 CC||tgdev...@gmail.com

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

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

[plasmashell] [Bug 487395] Plasmashell freezes when taking screenshot

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #9 from Nate Graham  ---
Thanks for doing a lot of debugging already and the scripts that you can use to
reproduce the issue. This is all super helpful. Sorry we didn't get to this
until now. It looks like something about saving the PNG into the history is
causing the slowdown.

Happily, I'm testing this with git master and I can't reproduce the issue with
your reproducer test case. In Plasma 6.3 we switched Klipper to use Sqlite for
the backend; can you see if this (or any other changes) have fixed the issue
for you in Plasma 6.3 or later? Thanks a lot!

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

[i18n] [Bug 142178] typo (es): kwrite and kate: " Usar espacios para sangrar en lugar de pestañas"

2025-04-06 Thread Dijalvan

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

Dijalvan  changed:

   What|Removed |Added

 CC||contato...@aol.com

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

[plasmashell] [Bug 478703] SD card is sometimes not detected in Disks and Devices when inserted

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #6 from Nate Graham  ---
Sorry we were not able to get to this yet. Can I ask you to please check to see
if it's still an issue with Plasma 6.3?

If it does still happen in Plasma 6.3 or later, can you also try in a new clean
user account to see if it works there?

Thanks a lot!

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

[plasmashell] [Bug 502480] Plasma 6.3.4 breaks Panel Colorizer

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---
Is there any problem when *not* using Panel Colorizer?

If everything is fine in that case, then probably this is a case where a bug we
fixed caused the issue by inverting an inappropriate workaround that Panel
Colorizer was applying; possibly this was
https://invent.kde.org/plasma/libplasma/-/commit/f37ea393ff97ec5b8ac66ed33028e5c7b7539659.

If removing or discontinuing the use of Panel Colorizer resolves the issue for
you, I'd recommend reporting this its developer, referencing the information
I've provided here.

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

[plasmashell] [Bug 502480] Plasma 6.3.4 breaks Panel Colorizer

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

Nate Graham  changed:

   What|Removed |Added

 CC||niccolo.venera...@gmail.com
Version|git-stable-Plasma/6.3   |6.3.4
  Component|"Manage Desktop and Panels" |Panel
   |window  |

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

[krita] [Bug 502472] Krita 5.3.0 prealpha df5e19f8 : very laggy search function

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

Freya Lupen  changed:

   What|Removed |Added

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

--- Comment #1 from Freya Lupen  ---
Confirmed. It also happens on 5.2.x if the resource cache was modified by
5.3.x.

Related MR: https://invent.kde.org/graphics/krita/-/merge_requests/2368

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

[krita] [Bug 502484] Layer Merging

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

--- Comment #1 from Freya Lupen  ---
Sounds like you accidentally triggered Flatten Image, the default shortcut for
it is Ctrl+Shift+E.  It can be undone (Ctrl+Z).

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

[KleverNotes] [Bug 502402] Notes disappeared after trying to move folders

2025-04-06 Thread farid

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

--- Comment #4 from farid  ---
(In reply to Louis Schul from comment #3)
> > In the end I didn't do it because it was confusing.
> 
> Just to be sure : 
> You cancelled the operation by clicking on the cancel button or outside the
> dialog ? You did not move anything ?
> 

Yeah, I did not move anything...

> > The program somehow created an empty folder here:
> > /run/user/1000/doc/60132296/ 
> 
> I can maybe see how a folder was created. 
> The weird thing is the storage path being modified... The only place were
> the storage path is changed is inside the storage dialog (what you use to
> point to the correct one).
> 
> Thank you for all the info. I will investigate, but this one seems hard to
> replicate !

It is indeed a difficult one to replicate specially since I don't have any
useful info. Do close it if you like though, I'll keep my eye open on this...

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

[plasmashell] [Bug 502479] Cannot drag more than one icon to a panel at a time

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org,
   ||niccolo.venera...@gmail.com
  Component|"Manage Desktop and Panels" |Panel
   |window  |
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO
Version|master  |6.3.4

--- Comment #1 from Nate Graham  ---
Can you please be precise about what exactly you're doing and how you're doing
it? There are a lot of ways to do the things you've mentioned here, so I fear
we will go in circles while trying to reproduce or debug it.

Please read
https://community.kde.org/Get_Involved/Issue_Reporting#Step_6:_File_a_high-quality_Bugzilla_ticket
and add the missing information like steps to repdoduce, software versions,
etc.

Thanks!

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

[kwin] [Bug 493647] Portal file picker not modal with its parent window, which can cause various UX issues

2025-04-06 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #8 from Kai Uwe Broulik  ---
Edit File Type has nothing to do with the file picker. This would be solved by
[1], so please file a separate issue for that.

[1] https://invent.kde.org/frameworks/kio/-/merge_requests/1528

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

[KScreen] [Bug 482974] Resolution changes after switching off the monitor

2025-04-06 Thread boospy

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

--- Comment #24 from boospy  ---
I just updated to 25.04 to test. It behaved strangely again. But now there are
completely different messages in the logs. I think the 25.04 was probably too
early after all... here some snipped:

```
NVRM: krcWatchdogCallbackVblankRecovery_IMPL: NVRM-RC: RM has detected that 7
Seconds without a Vblank Counter Update on head:D0
nvidia-modeset: ERROR: GPU:0: Idling display engine timed out:
0xc67e:6:0:1224
[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID
0x6500] Failed to apply atomic modeset.  Error code: -22
NVRM: Xid (PCI::65:00): 16, Head 0003 Count 0009b4ee
[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID
0x6500] Flip event timeout on head 0
```

I suspect that this is probably exclusively related to the very new kernel and
Nvidia drivers. I'll switch to Wayland and test it. It seems to be really
completely smooth and stable now. But only time will tell if this is really the
case.

Have a nice day :)

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

[krita] [Bug 502484] Layer Merging

2025-04-06 Thread Halla Rempt

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

Halla Rempt  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
   Severity|major   |normal
 CC||ha...@valdyas.org
 Status|REPORTED|RESOLVED

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

[kwin] [Bug 501073] kwin gets locked up playing a youtube video in firefox and "kwin_wayland_drm: The main thread was hanging temporarily!"

2025-04-06 Thread PolarisPyra

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

PolarisPyra  changed:

   What|Removed |Added

 CC||tmillerklug...@gmail.com

--- Comment #34 from PolarisPyra  ---
After being able to test again this morning It does seem to be related to
powerdevil. I clicked on the youtube link in the bugs description and
everything froze. After it unfroze (after maybe 1m) i restarted powerdevil  ```
systemctl --user restart plasma-powerdevil.service``` and tried again and it
worked. My system specs are as follows

GPU: Nvidia 4070
CPU: AMD 7700X
MOBO: B650 GAMING X AX V2 (rev. 1.x) 
Kernel: 6.13.8-arch1-1
KDE: 6.3.4
Graphics Platform:  Wayland

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

[plasmashell] [Bug 502485] New: Plasma crash with KDE partition manager

2025-04-06 Thread Fred Albrecht

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

Bug ID: 502485
   Summary: Plasma crash with KDE partition manager
Classification: Plasma
   Product: plasmashell
   Version: 6.2.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: f...@fredshome.org
  Target Milestone: 1.0

Application: plasmashell (6.2.1)

ApplicationNotResponding [ANR]: false
Qt Version: 6.7.2
Frameworks Version: 6.7.0
Operating System: Linux 6.13.9-200.fc41.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 41 (KDE Plasma)"
DrKonqi: 6.2.1 [CoredumpBackend]

-- Information about the crash:
Plasma crashed after the KDE partition manager created a 2 TB f2fs partition on
an external NVme drive. It may be related to the drive then being mounted.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: plasmashell (plasmashell), 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.

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

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

warning: Can't open file /memfd:kwin-dmabuf-feedback-table (deleted) during
file-backed mapping note processing

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

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

warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during
file-backed mapping note processing

warning: Can't open file
/home/fred/.cache/plasmashell/qmlcache/b61bba92706f814070c8dc116140eed4e5f54ba1.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file /home/fred/.cache/plasma_theme_default.kcache
(deleted) during file-backed mapping note processing

warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed
mapping note processing
[New LWP 2188]
[New LWP 2562]
[New LWP 81505]
[New LWP 2246]
[New LWP 2248]
[New LWP 2244]
[New LWP 2258]
[New LWP 2242]
[New LWP 2236]
[New LWP 2250]
[New LWP 2247]
[New LWP 2241]
[New LWP 2261]
[New LWP 2467]
[New LWP 2263]
[New LWP 2473]
[New LWP 2469]
[New LWP 2354]
[New LWP 2260]
[New LWP 3269]
[New LWP 4339]
[New LWP 2475]
[New LWP 2262]
[New LWP 166861]
[New LWP 3271]
[New LWP 2455]
[New LWP 3281]
[New LWP 81502]
[New LWP 2464]
[New LWP 3277]
[New LWP 2474]
[New LWP 2466]
[New LWP 2476]
[New LWP 7335]
[New LWP 2468]
[New LWP 2569]
[New LWP 2472]
[New LWP 4337]
[New LWP 81501]
[New LWP 2249]
[New LWP 2470]
[New LWP 3275]
[New LWP 81477]
[New LWP 84580]
[New LWP 4343]
[New LWP 3272]
[New LWP 7338]
[New LWP 4341]
[New LWP 269877]
[New LWP 81504]
[New LWP 7336]
[New LWP 81476]
[New LWP 84579]
[New LWP 166862]
[New LWP 81499]
[New LWP 84578]
[New LWP 4340]
[New LWP 7339]
[New LWP 81500]
[New LWP 81478]
[New LWP 81479]
[New LWP 166860]
[New LWP 166865]
[New LWP 2245]
[New LWP 84582]
[New LWP 3276]
[New LWP 166864]
[New LWP 166866]
[New LWP 2259]
[New LWP 2465]
[New LWP 166863]
[New LWP 81503]
[New LWP 84577]
[New LWP 4342]
[New LWP 4338]
[New LWP 7333]
[New LWP 7337]
[New LWP 7334]
[New LWP 84576]
[New LWP 84581]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f53de87fb54 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f53d89c9d40 (LWP 2188))]
Cannot QML trace cores :(
/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py:516: DeprecationWarning:
datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in
a future version. Use timezone-aware objects to represent datetimes in UTC:
datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
  boot_time =
datetime.utcfromtimestamp(psutil.boot_time()).strftime('%Y-%m-%dT%H:%M:%S')
/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py:533: DeprecationWarning:
datetime.datetime.utcnow() is deprecated and scheduled for removal in a future
version. Use timezone-aware objects to represent datetimes in UTC:
datetime.datetime.now(datetime.UTC).
  'timestamp': datetime.utcnow().isoformat(),
[Current thread is 1 (Thread 0x7f53d89c9d40 (LWP 2188))]

Thread 80 (Thread 0x7f522e7fc6c0 (LWP 84581)):
#0  0x7f53de87a7e9 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7f53de87cf8e in pthread_cond_wait@@GLIBC_2.3.2 () from
/

[plasmashell] [Bug 502485] Plasma crash with KDE partition manager

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

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

Thank you for the bug report!

However Plasma 6.2.1 is no longer eligible for support or maintenance from KDE;
supported versions are 5.27. (LTS), and 6.3 (non-LTS) or newer. Please upgrade
to a supported version as soon as your distribution makes it available to you.
Plasma is a fast-moving project, and bugs in one version are often fixed in the
next one.

If you need support for Plasma 6.2.1, please contact your distribution, who
bears the responsibility of providing support for older releases that are no
longer supported by KDE.

If you can reproduce the issue after upgrading to a supported version, feel
free to re-open this bug report.

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

[plasmashell] [Bug 485700] plasmashell crashes in QQuickMouseArea::mouseMoveEvent() while reordering Favorites in Application Launcher

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #6 from Nate Graham  ---
Can I ask you to please check to see if it's still an issue with Plasma 6.3
with Qt 6.8.2 or later?

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

[plasmashell] [Bug 491709] Plasmashell freeze upon animation

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #7 from Nate Graham  ---
These look to be all upstream in Qt. Can I ask you to please check to see if
it's still an issue with Plasma 6.3 with Qt 6.8.2 or later? Thanks a lot!

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

[plasmashell] [Bug 491846] Plasmashell crashes in QRegularExpressionPrivate::cleanCompiledPattern() after playing with monitor settings

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
Can I ask you to please check to see if it's still an issue with Plasma 6.3
with Qt 6.8.2 or later? Thanks a lot!

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

[KScreen] [Bug 502486] New: Shortcut for Display Configuration does not work anymore

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

Bug ID: 502486
   Summary: Shortcut for Display Configuration does not work
anymore
Classification: Plasma
   Product: KScreen
   Version: 6.3.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: OSD and Plasma applet
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: giugal...@gmail.com
  Target Milestone: ---

SUMMARY
I was able to switch the display configuration with Meta+P but since recently,
this does not work anymore. Shortcuts are still set in the system setting.
There are multiple reports on reddit about this
https://www.redditmedia.com/r/kde/comments/1jozg19/metap_doesnt_show_anything_anymore/.

STEPS TO REPRODUCE
1. Connect a second display
2. Hit Meta+P

OBSERVED RESULT
On-screen display does not pop. Display configuration can be changed in the
system setting, though.

EXPECTED RESULT
On-screen display pops up. Changes can be done using either shortcut or system
settings.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.13.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 7940HS with Radeon 780M Graphics
Memory: 14.8 GiB of RAM
Graphics Processor 1: AMD Radeon 780M
Graphics Processor 2: zink Vulkan 1.4
Manufacturer: LENOVO
Product Name: 82Y5
System Version: Legion Slim 5 14APH8

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 483514] With dual-screen setup where each screen has its own panel, most of the time on boot one screen's panel is on the screen

2025-04-06 Thread Jet

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

Jet  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---

--- Comment #10 from Jet  ---
(In reply to Nate Graham from comment #9)
> There have been a lot of changes and improvements to panel positioning
> recently. Can I ask you to try again with Plasma 6.3 or later and see if
> it's still happening? Thanks a lot!

It is still happening, but *slightly* less frequently, other than that exactly
as originally described. 
Still no idea if its linked to anything

KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.12.21-1-lts (64-bit)
Graphics Platform: Wayland

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

[plasmashell] [Bug 488717] Application launcher won't launch with hotkey when the panel is hidden and focused on another window.

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
Can I ask you to please check to see if it's still an issue with Plasma 6.3 or
later? Thanks!

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

[kwin] [Bug 493647] Portal file picker not modal with its parent window, which can cause various UX issues

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[plasmashell] [Bug 483514] With dual-screen setup where each screen has its own panel, most of the time on boot one screen's panel is on the screen

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #9 from Nate Graham  ---
There have been a lot of changes and improvements to panel positioning
recently. Can I ask you to try again with Plasma 6.3 or later and see if it's
still happening? Thanks a lot!

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

[plasmashell] [Bug 492013] Starting an activity (also tapping on an application icon in the icons only task manager sometimes) crashes plasmashell

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #3 from Nate Graham  ---
This looks to be all upstream in Qt. Can I ask you to please check to see if
it's still an issue with Plasma 6.3 with Qt 6.8.2 or later? Thanks a lot!

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

[plasmashell] [Bug 491954] Global Menu fails to display shortcuts for applications built with XfceGtkActionEntries

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Nate Graham  ---
It appears you are correct.

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

[plasmashell] [Bug 485594] On X11, Panel moves up when starting an application

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO
   Keywords||X11-only

--- Comment #7 from Nate Graham  ---
Sorry we were not able to get to this yet. Can I ask affected people to please
check to see if it's still an issue with Plasma 6.3 or later? Thanks!

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

[plasmashell] [Bug 470410] kmail windows list text in plasma window list with symbols only appears heads-down

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #9 from Nate Graham  ---
Unfortunately I've still never been able to reproduce this. Can I ask you to
please check to see if it's still an issue with Plasma 6.3 or later? Thanks!

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

[kate] [Bug 499865] Kate will crash if accessing a text file on the network and the network goes down

2025-04-06 Thread jimbo

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

--- Comment #13 from jimbo  ---
> reopening as obtaining a backtrace is non trivial for a non technical user

Unfortunately, I still don't have free time to follow this up. I'm still
interested in a fix, and it's on my todo list... and I'll get to it, but a bot
janny sweeping bugs from reporters within 15 days is hilarious. The developers
aren't held to this standard, but reporters have to respond after 15 days? The
developers are volunteers along with the bug reporters, but you want to put us
on a deadline? Either do the same for developers or why should anyone report?
Fuck this deadline shit.

I'm eyeballs deep in other stuff at the minute, I'll get around to it when I
have spare time. "WORKSFORME" is probably the worst concept ever devised and
will drive people away from even reporting. I've only seen this 'WORKSFORME'
occur recently, which is pure bollocks. It goes from 'NEEDSINFO', to no info
provided, and then suddenly to "WORKSFORME". How does that even make sense? A
bug is provided, no info for 30 days and then suddenly "WORKSFORME", yeah,
brilliant.

I'll get back to you when I find the time, put a deadline on it and I'm fucking
out.

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

[kate] [Bug 499865] Kate will crash if accessing a text file on the network and the network goes down

2025-04-06 Thread Christoph Cullmann

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

--- Comment #14 from Christoph Cullmann  ---
I agree that sometimes that bot is not helpful, but even if it closes the bug,
you can still provide the info whenever you like and just re-open it.

That is close to zero extra effort.

Without automation like this, we will just be swamped with stuff.

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

[Qt/KDE Flatpak Runtime] [Bug 502434] org.kde.Sdk: Probable missmatch in provided stdlibs

2025-04-06 Thread Ardith Metz

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

Ardith Metz  changed:

   What|Removed |Added

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

--- Comment #1 from Ardith Metz  ---
Looks like you are running this test command directly on host system outside
flatpak environment. If you want to test flatpak you need to launch it first -
either from desktop file or by opening shell inside through:

flatpak run --command=sh io.qt.QtCreator

Then you may test any relevant commands.

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

[Discover] [Bug 456362] Show more details while fetching updates

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

jos...@gmail.com changed:

   What|Removed |Added

 CC||jos...@gmail.com

--- Comment #5 from jos...@gmail.com ---
Discover 6.3.3 got me today while testing Fedora 42 pre-release. "Fetching
updates" progress bar was stuck for over 10 minutes and I had no idea what was
happening. What's even worse, until updates are fetched, I cannot install any
rpm packages and cannot see installed packages.
Only after running `dnf update` I understood what was happening: package
repository was especially slow, downloading data at ~10KB/s speed. But dnf
displayed a progress bar and even time estimate until completion. At the end I
left PC and after hour Discover had completed fetching updates. It would be
very useful for casual users to have similar information (download speed and
estimate) visible in Discover.

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

[okular] [Bug 502482] New: D-Bus Methods in Okular Do Not Work Correctly for Specific Tabs

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

Bug ID: 502482
   Summary: D-Bus Methods in Okular Do Not Work Correctly for
Specific Tabs
Classification: Applications
   Product: okular
   Version: 24.05.2
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: matthiasschmitz1...@gmail.com
  Target Milestone: ---

SUMMARY
When multiple pdfs are open in different tabs within the same Okular instance,
D-Bus methods like currentPage, currentDocument, and goToPage do not behave as
expected. 

STEPS TO REPRODUCE
1. In Okluar go to "Settings" -> "Configure Okular..." -> "General" -> activate
"Open new files in tabs"
2. Open multiple pdfs in tabs of the same Okular instance
3.  Run "qdbus org.kde.okular-{PROCESS ID} /okular org.kde.okular.currentPage"

OBSERVED RESULT
The method (currentPage) always returns a result for the initially opened
document and not the currently activate tab. The same issue occurs with other
methods (e.g., currentDocument, slotPreviousPage, slotNextPage, etc...).

If the tab of the initially opened document is closed, but the okular instance
is still open with another document, then qdbus returns an error.

EXPECTED RESULT
I would expect the methods to work for the currently active tab by default. I
would also expect an option to use the methods on multiple different tabs, even
when not active.

SOFTWARE/OS VERSIONS
Linux: Ubuntu 24.10
okular: 24.05.2
Qt Version: 5.15.15

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

[kwin] [Bug 502203] Stylus stopped working in Wayland, but works in X11. The Systems detects the stylus but the cursor doesn’t follow it.

2025-04-06 Thread Andre85

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

--- Comment #2 from Andre85  ---
Hello. Thanks for helping.

This is the content of kcminputrc:

[Libinput][1267][10009][ELAN0732:00 04F3:2719 Stylus]
CalibrationMatrix=-1.341104507446289e-07,-7.543712854385376e-08,-6.063298192519884e-13,0,1.0761949909010582e-07,6.05359673500061e-08,-5.0527483808288434e-14,0,0,0,1,0,0,0,0,1
MapToWorkspace=false
Orientation=0
OutputArea=0,0,1,1
OutputName=

[Libinput][2][7][SynPS/2 Synaptics TouchPad]
ClickMethod=1
DisableEventsOnExternalMouse=true
NaturalScroll=true
PointerAcceleration=0.200
PointerAccelerationProfile=1

[Mouse]
X11LibInputXAccelProfileFlat=true

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

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

2025-04-06 Thread Evert Vorster

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

--- Comment #101 from Evert Vorster  ---
I spoke too soon, after a suspend-resume cycle, I could see the memory counting
up in kwin_wayland just sitting there, with nothing happening on screen. 

So, false alarm, 6.14 kernel does not, in fact, cure this issue.

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

[frameworks-kio] [Bug 502319] Graphical glitch ("depression") when hovering over items in open dialog / file picker

2025-04-06 Thread Massimiliano L

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

--- Comment #1 from Massimiliano L  ---
Can confirm that:
- the issue does not depend on the application invoking the dialog being a
Flatpak (can reproduce from KDE system settings)
- the issue does not depend on GPU (Intel Graphics and discrete AMD result in
the same behaviour)

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

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

2025-04-06 Thread Evert Vorster

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

--- Comment #100 from Evert Vorster  ---
For what it's worth, when using the 6.14 kernel this issue seems to be gone. 
I'm currently running linux-mainline on Arch.

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

[digikam] [Bug 465575] Face Recognition - Suggest Names

2025-04-06 Thread Andy

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

--- Comment #7 from Andy  ---
Hello Mike,

Yes, that works very well. New faces are constantly being recognized.

I might have some more ideas.
I suspect that recognition always starts with FaceID 1, then 2, 3, 4, etc.
Ignored faces are skipped.
If the automatic face search is running and digiKam is closed, the search will
not continue the next time the program is started. The function doesn't have to
remember every FaceID, but perhaps all 500 FaceIDs as a new starting point at
program startup?
Does automatic face recognition pause until the user's database accesses are
complete?

Regards
Andy

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

[kwin] [Bug 502481] Magnifier effect doesn't follow pen tablet stylus

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

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

Thank you for the bug report!

However Plasma 6.2.5 is no longer eligible for support or maintenance from KDE;
supported versions are 5.27. (LTS), and 6.3 (non-LTS) or newer. Please upgrade
to a supported version as soon as your distribution makes it available to you.
Plasma is a fast-moving project, and bugs in one version are often fixed in the
next one.

If you need support for Plasma 6.2.5, please contact your distribution, who
bears the responsibility of providing support for older releases that are no
longer supported by KDE.

If you can reproduce the issue after upgrading to a supported version, feel
free to re-open this bug report.

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

[kwin] [Bug 502203] Stylus stopped working in Wayland, but works in X11. The Systems detects the stylus but the cursor doesn’t follow it.

2025-04-06 Thread Andre85

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

--- Comment #3 from Andre85  ---
Regarding the libinput debug-events output, everithing seems to be OK. I tried
to make a swype fron the botom left cornet to the top right corner of the
screen.
I only posted the start and the end of the log, as it seemed enough.


➜  ~ sudo libinput debug-events
-event2   DEVICE_ADDED Power Button  seat0
default group1  cap:k
-event3   DEVICE_ADDED Video Bus seat0
default group2  cap:k
-event0   DEVICE_ADDED Power Button  seat0
default group3  cap:k
-event1   DEVICE_ADDED Lid Switchseat0
default group4  cap:S
-event7   DEVICE_ADDED ELAN0732:00 04F3:2719 seat0
default group5  cap:t  size 289x163mm ntouches 10 calib
-event10  DEVICE_ADDED ELAN0732:00 04F3:2719 Stylus  seat0
default group5  cap:T  size 293x165mm left calib
-event4   DEVICE_ADDED AT Translated Set 2 keyboard  seat0
default group6  cap:k
-event13  DEVICE_ADDED SynPS/2 Synaptics TouchPadseat0
default group7  cap:pg  size 69x51mm tap (dl off) left scroll-nat
scroll-2fg-edge click-buttonareas-clickfinger dwtp-on
-event11  DEVICE_ADDED HP WMI hotkeysseat0
default group8  cap:kS
-event5   DEVICE_ADDED Wireless hotkeys  seat0
default group9  cap:k
-event10  TABLET_TOOL_PROXIMITY+0.000s  2.16*/151.84*  
pressure: 0.00* pen  (0, id 0) proximity-in axes:p  btn:S
 event10  TABLET_TOOL_PROXIMITY+0.050s  2.16/151.84
pressure: 0.00  pen  (0, id 0) proximity-out
 event10  TABLET_TOOL_PROXIMITY+0.270s  0.97*/152.16*  
pressure: 0.00* pen  (0, id 0) proximity-in axes:p  btn:S
 event10  TABLET_TOOL_AXIS +0.278s  0.97/152.16
pressure: 0.03*
 event10  TABLET_TOOL_TIP  +0.284s  0.97/152.16
pressure: 0.05* down
 event10  TABLET_TOOL_AXIS +0.293s  0.97/152.16
pressure: 0.08*
 event10  TABLET_TOOL_AXIS  2  +0.299s  0.97/152.16
pressure: 0.11*
 event10  TABLET_TOOL_AXIS  3  +0.308s  0.97/152.16
pressure: 0.14*

 event10  TABLET_TOOL_AXIS672  +2.832s  288.14*/0.25*  
pressure: 0.69
 event10  TABLET_TOOL_AXIS673  +2.837s  288.29*/0.24*  
pressure: 0.69*
 event10  TABLET_TOOL_AXIS674  +2.839s  288.40*/0.22*  
pressure: 0.69
 event10  TABLET_TOOL_AXIS675  +2.844s  288.51*/0.21*  
pressure: 0.69*
 event10  TABLET_TOOL_AXIS676  +2.847s  288.60*/0.19*  
pressure: 0.69
 event10  TABLET_TOOL_AXIS677  +2.851s  288.70*/0.17*  
pressure: 0.69*
 event10  TABLET_TOOL_AXIS678  +2.854s  288.79*/0.17*  
pressure: 0.69
 event10  TABLET_TOOL_AXIS679  +2.859s  288.94*/0.17*  
pressure: 0.18*
 event10  TABLET_TOOL_AXIS680  +2.861s  289.00*/0.19*  
pressure: 0.18
 event10  TABLET_TOOL_TIP  +2.874s  288.98*/0.19   
pressure: 0.00* up
 event10  TABLET_TOOL_PROXIMITY+2.922s  288.98/0.19
pressure: 0.00  pen  (0, id 0) proximity-out

Please let me know if you need something more. 
Thank you.

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

[www.kde.org] [Bug 502483] New: IRC webchat link is dead on https://marble.kde.org/contributors-welcome.php

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

Bug ID: 502483
   Summary: IRC webchat link is dead on
https://marble.kde.org/contributors-welcome.php
Classification: Websites
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: zl2...@gmail.com
  Target Milestone: ---

IRC webchat link is dead on https://marble.kde.org/contributors-welcome.php

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

[Discover] [Bug 502145] List of installed apps scrolls up after click on the button to remove an app

2025-04-06 Thread Thomas Bertels

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

Thomas Bertels  changed:

   What|Removed |Added

 CC||tbert...@gmail.com

--- Comment #2 from Thomas Bertels  ---
Depending on which app you try to uninstall, this can actually make you
uninstall a different app without noticing it if its uninstall button ends up
just below the mouse pointer when you release the left click button.

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

[umbrello] [Bug 502347] Cut > Open > Fit crashes Umbrello with a segfault

2025-04-06 Thread Ralf Habacker

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

Ralf Habacker  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/sdk/
   ||umbrello/-/commit/766ac2cd7
   ||2a5511feaee979f9a2d9ba50658
   ||6161
 Resolution|--- |FIXED
   Version Fixed In||25.04.0
 Status|REPORTED|RESOLVED

--- Comment #1 from Ralf Habacker  ---
Git commit 766ac2cd72a5511feaee979f9a2d9ba506586161 by Ralf Habacker.
Committed on 06/04/2025 at 12:23.
Pushed by habacker into branch 'release/25.04'.

Fix crash bug on pressing 'Fit' or '100%' when no diagram is available
FIXED-IN:25.04.0

M  +10   -0umbrello/uml.cpp

https://invent.kde.org/sdk/umbrello/-/commit/766ac2cd72a5511feaee979f9a2d9ba506586161

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

[dolphin] [Bug 502476] New: An eject button is not showing to eject my removable Android phone

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

Bug ID: 502476
   Summary: An eject button is not showing to eject my removable
Android phone
Classification: Applications
   Product: dolphin
   Version: 24.12.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: mostafa2018...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

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

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

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

SUMMARY


STEPS TO REPRODUCE
1. Connect an Android phone (mine is Xiaomi Redmi Note 8 Pro)
2. Search everywhere for an unmount button
3. You will not find one, even with the search functionality of Dolphin!

OBSERVED RESULT
No "unmount" button showing 

EXPECTED RESULT
Some "unmount" button to be able to safely unmount my device instead of
removing it and hoping that no data gets corrupted!

KINFO
libEGL warning: egl: failed to create dri2 screen
Operating System: Arch Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.13.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i7-12650H
Memory: 15.2 GiB of RAM
Graphics Processor 1: Mesa Intel® Graphics
Graphics Processor 2: zink Vulkan 1.4

ADDITIONAL INFORMATION
None

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

[dolphin] [Bug 502477] New: An eject button is not showing to eject my removable Android phone

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

Bug ID: 502477
   Summary: An eject button is not showing to eject my removable
Android phone
Classification: Applications
   Product: dolphin
   Version: 24.12.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: mostafa2018...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

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

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

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

SUMMARY


STEPS TO REPRODUCE
1. Connect an Android phone (mine is Xiaomi Redmi Note 8 Pro)
2. Search everywhere for an unmount button
3. You will not find one, even with the search functionality of Dolphin!

OBSERVED RESULT
No "unmount" button showing 

EXPECTED RESULT
Some "unmount" button to be able to safely unmount my device instead of
removing it and hoping that no data gets corrupted!

KINFO
libEGL warning: egl: failed to create dri2 screen
Operating System: Arch Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.13.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i7-12650H
Memory: 15.2 GiB of RAM
Graphics Processor 1: Mesa Intel® Graphics
Graphics Processor 2: zink Vulkan 1.4

ADDITIONAL INFORMATION
None

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

[dolphin] [Bug 502477] An eject button is not showing to eject my removable Android phone

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

Mostafa Beder  changed:

   What|Removed |Added

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

--- Comment #1 from Mostafa Beder  ---


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

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

[dolphin] [Bug 502476] An eject button is not showing to eject my removable Android phone

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

--- Comment #1 from Mostafa Beder  ---
*** Bug 502477 has been marked as a duplicate of this bug. ***

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

[kmymoney] [Bug 502461] Merge categories and delete old

2025-04-06 Thread Thomas Baumgart

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

Thomas Baumgart  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #3 from Thomas Baumgart  ---
Problem duplicated. The process did not change. Fix pending.

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

[krita] [Bug 502471] Internal Errors - Krita 5.3.0 prealpha df5e19f

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

Freya Lupen  changed:

   What|Removed |Added

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

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


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

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

[KleverNotes] [Bug 502402] Notes disappeared after trying to move folders

2025-04-06 Thread Louis Schul

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

Louis Schul  changed:

   What|Removed |Added

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

--- Comment #3 from Louis Schul  ---
> In the end I didn't do it because it was confusing.

Just to be sure : 
You cancelled the operation by clicking on the cancel button or outside the
dialog ? You did not move anything ?

> The program somehow created an empty folder here:
> /run/user/1000/doc/60132296/ 

I can maybe see how a folder was created. 
The weird thing is the storage path being modified... The only place were the
storage path is changed is inside the storage dialog (what you use to point to
the correct one).

Thank you for all the info. I will investigate, but this one seems hard to
replicate !

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

[kdeconnect] [Bug 502427] Phone and computer can't be paired; they briefly appear available to the other and then disappear

2025-04-06 Thread Albert Vaca Cintora

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

Albert Vaca Cintora  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Vaca Cintora  ---
Hey Nate, thanks for reporting this. 

I know of at least another uses with the same problem, so it's definitely a
bug. I can't reproduce it, though, so it doesn't affect all devices. 

It would be useful to see the logs from the Android side when this happens,
because the desktop side seems fine. I just released KDE Connect Android
version 1.33.3 which includes a new option to get the logs from within the KDE
Connect app itself. When you get the 1.33.3 update in a couple days, can you go
to "Settings -> Export KDE Connect Logs" and attach the generated file? 

There's also a small chance that 1.33.3 fixes the issue, since it includes some
fixes, but most likely this is a different problem.

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

[kmymoney] [Bug 502306] Inclusion of Opening Balances in Net Worth Report on a Specific Date

2025-04-06 Thread Ralf Habacker

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

Ralf Habacker  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
 CC||ralf.habac...@freenet.de

--- Comment #4 from Ralf Habacker  ---
(In reply to origamy.39 from comment #3)
...
> Important Feature Suggestion:

See https://kmymoney.org/support.html how to file a feature request.

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

[plasmashell] [Bug 502479] New: Cannot drag more than one icon to a panel at a time

2025-04-06 Thread ProtonMan

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

Bug ID: 502479
   Summary: Cannot drag more than one icon to a panel at a time
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: "Manage Desktop and Panels" window
  Assignee: plasma-b...@kde.org
  Reporter: ccc...@proton.me
  Target Milestone: 1.0

A few days ago I installed latest CachyOS ISO selecting Plasma, added my panels
and when I go to drag apps to any of them I can only drag one to that panel
then I have to logout and back in to drag another one. I have never seen this
behavior before any thoughts on what might be causing the issue.

Yesterday I went to setup BlueStar linux and got the same behavior. See my
thread on the forum.

https://discuss.kde.org/t/cannot-drag-more-than-one-icon-to-a-panel-at-a-time/32335/1

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

[plasmashell] [Bug 502480] New: Plasma 6.3.4 breaks Panel Colorizer

2025-04-06 Thread ProtonMan

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

Bug ID: 502480
   Summary: Plasma 6.3.4 breaks Panel Colorizer
Classification: Plasma
   Product: plasmashell
   Version: git-stable-Plasma/6.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: "Manage Desktop and Panels" window
  Assignee: plasma-b...@kde.org
  Reporter: ccc...@proton.me
  Target Milestone: 1.0

Once the Plasma 6.3.4 update is installed and one reboots Panel Colorizer no
longer behaves correctly. After the reboot I booted to have black text instead
of white text on the main panel, and the other panels with a black background
instead of transparent with blur.  This is not distro specific, this is after
the Plasma 6.3.4 update.

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

[frameworks-kimageformats] [Bug 502474] kimageformats fails to build with OpenEXR 3.3.3

2025-04-06 Thread Antonio Rojas

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

--- Comment #1 from Antonio Rojas  ---
This looks like a mismatch bewteen the openexr and imath versions used at build
time (ie. you're building against system openexr, which I assume links to a
system imath, yet you are using with a custom imath), rather than a problem in
kimageformats. FWIW it builds fine here using openexr 3.3.

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

[kdeconnect] [Bug 502478] New: Peer discovery seems to still have a race condition in handshake on some devices

2025-04-06 Thread Daniel Landau

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

Bug ID: 502478
   Summary: Peer discovery seems to still have a race condition in
handshake on some devices
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Android 12.x
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: dan...@landau.fi
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY

I can't reproduce it, but there have been numerous reports of protocol v8
devices showing up and disappearing on the GSConnect github repo.

One of the reports
(https://github.com/GSConnect/gnome-shell-extension-gsconnect/issues/1980#issuecomment-2766411619)
came with a useful looking adb logcat, that seems to indicate that Device.kt is
firing off some packet while LanLinkProvider.java is still trying to do the
secure identity packet exchange, causing conscrypt to go haywire similarly but
different than in the issue fixed in 1.33.2. Actually according to
https://bugs.kde.org/show_bug.cgi?id=501635#c6, it might be that this reliably
reproducing racyness might even caused by that fix.

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

[kwin] [Bug 493647] Portal file picker not modal with its parent window, which can cause various UX issues

2025-04-06 Thread Christian Hartmann

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

Christian Hartmann  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
Product|xdg-desktop-portal-kde  |kwin
  Component|general |general

--- Comment #7 from Christian Hartmann  ---
same issue with:  

Changing the properties of a file type in Dolphin.  "Edit File Type" dialog
opens in top left corner of a different screen than the first opened
"Properties" dialog.  

changed back(?) to kwin Product.

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

[marble] [Bug 474534] MapQuest routing doesn't work

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

--- Comment #1 from zl2...@gmail.com ---
Created attachment 180043
  --> https://bugs.kde.org/attachment.cgi?id=180043&action=edit
hopefully fixes it

I don't have a MapQuest API key anymore so can't test it.

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

[plasmashell] [Bug 450551] Battery charge limit is not preserved after reboot on many laptops that support charge limits; need to write it on every boot

2025-04-06 Thread Rock

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

Rock  changed:

   What|Removed |Added

 CC||rocafue...@tutamail.com

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

[plasmashell] [Bug 436770] GPU sensors do not work with intel iGPU

2025-04-06 Thread Ilya Bizyaev

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

Ilya Bizyaev  changed:

   What|Removed |Added

 CC||bizy...@pm.me

--- Comment #9 from Ilya Bizyaev  ---
Relevant: https://invent.kde.org/plasma/ksystemstats/-/merge_requests/98

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

[kdeconnect] [Bug 502409] KDE Connect 25.03.90 no longer shows connected devices

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

Eliseu Amaro  changed:

   What|Removed |Added

 CC||m...@eliseuama.ro

--- Comment #1 from Eliseu Amaro  ---
Same is happening to me, KSystemLog is showing the following everytime I
refresh the devices list:

2025-04-06 16:30kdeconnectd 2025-04-06T16:30:31 kdeconnect.core:
Invalid identity packet received
2025-04-06 16:30kdeconnectd 2025-04-06T16:30:32 kdeconnect.core:
Invalid identity packet received
2025-04-06 16:30kdeconnectd 2025-04-06T16:30:32 kdeconnect.core:
LanLinkProvider/newConnection: Host timed out without sending any identity.
QHostAddress(":::192.168.0.25")
2025-04-06 1:30 kdeconnectd 2025-04-06T16:30:33 kdeconnect.core:
LanLinkProvider/newConnection: Host timed out without sending any identity.
QHostAddress(":::192.168.0.25")

SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.6
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.4.0-150600.23.42-default (64-bit)
Graphics Platform: Wayland

Smartphone KDE Connect version: FDroid 1.33.2

KDE Connect: 25.03.90
openSUSE Leap 15.6 (Wayland)
KDE Frameworks: 6.12.0
Qt: Using 6.9.0 and built against 6.9.0
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.4.0-150600.23.42-default

Interestingly, on NixOS nightly, using GNOME with GSConnect, I am able to
connect to my phone. So, I think the issue lies with KDE Connect on Linux.

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

[kdeconnect] [Bug 501635] KDE Connect: Android 13 and Android 14 cannot search for each other, nor can they be added to the list by IP

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

Eliseu Amaro  changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 502409] KDE Connect 25.03.90 no longer shows connected devices

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

--- Comment #3 from Eliseu Amaro  ---
Have added the bug report that helped me out, see above under "See Also:".

There, the last comment reads:
> there are two main reasons that can cause this -and related issues-:
> - you are not running an updated desktop version 25.xx.xx (protocol mismatch)
> - or you -initially- installed an android version older than 1.24.x (short
> device-id)
> 
> solutions:
> - for the first, if you can't upgrade the desktop version, you must
> downgrade the android version below 1.33.x, a protocol version change made
> untrusted devices not visible.
> - for the second, the device-id auto-generated by android is too short (< 32
> chars) and the newer protocol doesn't support it, you can check this by
> looking up your device on ~/.config/kdeconnnect/trusted_devices, the section
> name is your device-id. if this is the case you need to delete your app data
> and pair again your device. after that you _might_ upgrade your android
> version.
> 
> 
> some of this info was taken from github.com/metallkopf/konnect

For me, clearing storage and cache on KDE Connect on my cellphone fixed the
issue.

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

[kdeconnect] [Bug 502409] KDE Connect 25.03.90 no longer shows connected devices

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

Eliseu Amaro  changed:

   What|Removed |Added

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

--- Comment #4 from Eliseu Amaro  ---


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

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

[digikam] [Bug 502487] New: Auto-Rotate does not work correct when more than one image is selected in thumbnail view

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

Bug ID: 502487
   Summary: Auto-Rotate does not work correct when more than one
image is selected in thumbnail view
Classification: Applications
   Product: digikam
   Version: 8.7.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Thumbs-IconView
  Assignee: digikam-bugs-n...@kde.org
  Reporter: braun@gmail.com
  Target Milestone: ---

related to 502200
If more than one image is selected in thumbnail view and auto-rotated
(Ctrl/Shift up), the result is often wrong. (Tested with 5 and 100 images)
If only one image is selected, auto-rotate works fine.
This was tested with nightly build from Saturday 2025-04-05 with both tiff and
jpg files.

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

[digikam] [Bug 443827] Clicking on a person with unconfirmed suggestions does not always focus on these suggestions

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

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

   What|Removed |Added

Version|8.0.0   |8.6.0

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

[digikam] [Bug 443827] Clicking on a person with unconfirmed suggestions does not always focus on these suggestions

2025-04-06 Thread MarcP

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

--- Comment #10 from MarcP  ---
Hi, I've been doing some tagging today, and I can confirm the issue is still
valid.

It's quite annoying, because when you are in the suggestions section of the
face, confirm a suggestion, then the focus changes to a previously selected
picture for that person, so that means you need to manually scroll up and find
where you left off, for every single face you tag.

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

[digikam] [Bug 413842] Wishlist: search not sensitive to special characters / diacritics

2025-04-06 Thread MarcP

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

MarcP  changed:

   What|Removed |Added

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

--- Comment #6 from MarcP  ---
Hi, can we please reopen this one? Having an accent-insensitive search would
really be convenient.

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

[digikam] [Bug 502487] Auto-Rotate does not work correct when more than one image is selected in thumbnail view

2025-04-06 Thread Michael Miller

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

Michael Miller  changed:

   What|Removed |Added

 CC||michael_mil...@msn.com

--- Comment #1 from Michael Miller  ---
(In reply to Braun.Lot from comment #0)
> related to 502200
> If more than one image is selected in thumbnail view and auto-rotated
> (Ctrl/Shift up), the result is often wrong. (Tested with 5 and 100 images)
> If only one image is selected, auto-rotate works fine.
> This was tested with nightly build from Saturday 2025-04-05 with both tiff
> and jpg files.

Thank you, Lothar.  I think this might be related to #502455.  I'll need Gilles
or Maik's help to figure it out.

Cheers,
Mike

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

[dolphin] [Bug 501572] Clicking Empty Trash at specific locations within Dolphin, then cancelling when confirmation is requested, still causes the Trash: Emptied notification sound to play

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

--- Comment #3 from elydgol...@gmail.com ---
Can reproduce on openSUSE Tumbleweed 20250403

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

[plasmashell] [Bug 486664] Some translations on the Breeze-themed SDDM theme are not used

2025-04-06 Thread Emir SARI

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

Emir SARI  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #3 from Emir SARI  ---
This is no longer reproducible in the latest neon version.

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

[plasmashell] [Bug 502488] New: Disks and Devices widget gets stuck in BS "Removing..." or "Don't unplug yet..." state and stops responding for a long time when USB drive

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

Bug ID: 502488
   Summary: Disks and Devices widget gets stuck in BS
"Removing..." or "Don't unplug yet..." state and stops
responding for a long time when USB drive
Classification: Plasma
   Product: plasmashell
   Version: 6.3.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: php4...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

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

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

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

SUMMARY


STEPS TO REPRODUCE
1. Plug a USB pendrive into a USB prot
2. Click on the SUB connector icon that appears in the Tray area (Disks and
Devices)
3. Click "Mount and Open" next to the device name
4. Close the folder window/tab that opened in Dolphin
5. Go back to Disks and Devices and click "Safely remove"

EXPECTED RESULT
It shouldn't take long to safely remove the device in the first place
(especially since I didn't do anything with it), but if it does for a
legitimate reason, the UI should behave nicely

OBSERVED RESULT
The status text belos the device name now says "Removing..." and a spinning
icon appears on the right.
Sometimes, the text then changes to "Don't unplug yet, files are still being
transferred" or something like that (I'm quoting from memory, that's probably
not the exact wording), then the spinning icon sometimes freezes. Sometimes
this happens still at the "Removing..." stage
The icon of the "Disks and Devices" widget becomes a checkmark, which makes no
sense whatsoever
The widget stops responding, it doesn't close when you click outside of it,
when you explicitly click the "<-" arrow, nor when you click the down arrow at
the bottom, and **SOMETIMES THE ENTIRE SYSTEM** stops responding for a while,
which is why I'm marking this as "major".
I tried to take a screenshot with the keyboard shortcut for Spectacle once
while this was happening; it did nothing and a minute later I got an error
saying it failed to launch Spectacle - that's how unresponsive the system was.

After several seconds to one minute, the operation will complete and the system
will begin responding normally again. Sometimes, a few of the keyboard or mouse
actions that you attempted while the system was frozen will now have their
delayed effects all at once, which is another reason for setting the severity
to "major" and why you might consider changing it to "critical".

With a given pendrive of mine in particular (which happens to be a bootable
Memtest86 iso image) this is now happening almost systematically to me (but not
quite).

Note that whether or not there are actual legitimate reasons for the actual
"safe removal" operation to take a longer than expected time (which I don't
think is the case, but who knows, the usb memory stick itself might be faulty),
the UI should at all time remain responsive and never, ever, under any
circumstances, should the responsive of the entire system be affected.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.6.84-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × 12th Gen Intel® Core™ i7-1255U
Memory: 15.3 GiB of RAM
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: Vivobook_ASUSLaptop X1502ZA_F1502ZA
System Version: 1.0

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 501750] Activity switcher is non-functional unless I restart plasmashell

2025-04-06 Thread Quentin Guyot

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

Quentin Guyot  changed:

   What|Removed |Added

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

--- Comment #6 from Quentin Guyot  ---
Apparently this needs info.

1. I tried the suggestion. It changed nothing (as I already mentioned in
another comment).

2. Here's a maybe more thorough description:
-When i boot on my system (I auto login with SDDM if that helps), I can't
switch activities using the activity switcher.
-Sometimes I can switch activities with KRunner, sometimes not (I haven't found
the pattern yet.)
-If I want to be able to switch or manage activities with the sidebar, I need
to restart Plasmashell. I used to log out then back in in order to do that for
a while, until I realized I could just restart plasma with plasmashell
--replace (which is what I've been doing for a while.)

That's all that comes to mind. If you need more, ask and I'll answer.

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

[kdeconnect] [Bug 502409] KDE Connect 25.03.90 no longer shows connected devices

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

Eliseu Amaro  changed:

   What|Removed |Added

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

--- Comment #2 from Eliseu Amaro  ---
(In reply to Claudio from comment #0)
> SUMMARY
> After upgrading to KDE Connect 25.03.90 the desktop app can no longer see my
> Android devices and the other way around (Android APP version 1.33.2 from
> Google Play store).
> 
> STEPS TO REPRODUCE
> 1. Upgrade to 25.03.90
> 2. Reboot
> 
> OBSERVED RESULT
> KJournald shows:
> 
> kdeconnect.core: Invalid identity packet received
> kdeconnect.core: LanLinkProvider/newConnection: Host timed out without
> sending any identity. QHostAddress(":::XXX")
> 
> XXX= IPv4 of Android device
> Disabling firewalld completely didn't help
> 
> EXPECTED RESULT
> KDE Connect still working (downgrading only the kdeconnect package 24.12.3
> and restarting the service makes everything work again)
> 
> SOFTWARE/OS VERSIONS
> Operating System: EndeavourOS 
> KDE Plasma Version: 6.3.4
> KDE Frameworks Version: 6.12.0
> Qt Version: 6.9.0
> Kernel Version: 6.14.0-arch1-1 (64-bit)
> Graphics Platform: Wayland
> Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
> Memory: 125.7 GiB of RAM
> Graphics Processor: AMD Radeon RX 7800 XT
> Manufacturer: Micro-Star International Co., Ltd.
> Product Name: MS-7D50
> System Version: 1.0
> 
> ADDITIONAL INFORMATION

Hey! I have just found the solution!

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

[dolphin] [Bug 501572] Clicking Empty Trash at specific locations within Dolphin, then cancelling when confirmation is requested, still causes the Trash: Emptied notification sound to play

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

elydgol...@gmail.com changed:

   What|Removed |Added

 CC||elydgol...@gmail.com

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

[digikam] [Bug 502455] Rotate and Flip bug

2025-04-06 Thread HubMiner

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

--- Comment #3 from HubMiner  ---
Summary:
I reproduced the bug: the problematic behavior as Maik said: when images start
with non-Normal orientation flag - not 1.


Steps:

X Close Digikam
X move 2 files to clean test folder (no interaction with RAW or video pairs or
sidecar files).
X Delete sidecar files

X using exiftool, check preexisting orientation: 
Rotate 90 CW - 9

X using exiftool, reset orientation to "normal".
exiftool -n -Orientation=1 *.JPG

x start digikam.
x allow to sync the files.

x visually check orientation in DK: 
2 files need "1 right" rotation.

x select the 2 files.
X change the orientation together.
Expected behavor, rotated 90' - 1 step.

x update Digikam settings for orientation: set using a flag
x rotate to set Orientation to 6 (saved in xmp)

x select the 2 files.
x change the orientation together.
x result: unexpected behavor, rotated 180' - 2 steps.

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

[kdeconnect] [Bug 502409] KDE Connect 25.03.90 no longer shows connected devices

2025-04-06 Thread Claudio

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

Claudio  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED

--- Comment #5 from Claudio  ---
(In reply to Eliseu Amaro from comment #3)
> Have added the bug report that helped me out, see above under "See Also:".
> 
> There, the last comment reads:
> > there are two main reasons that can cause this -and related issues-:
> > - you are not running an updated desktop version 25.xx.xx (protocol 
> > mismatch)
> > - or you -initially- installed an android version older than 1.24.x (short
> > device-id)
> > 
> > solutions:
> > - for the first, if you can't upgrade the desktop version, you must
> > downgrade the android version below 1.33.x, a protocol version change made
> > untrusted devices not visible.
> > - for the second, the device-id auto-generated by android is too short (< 32
> > chars) and the newer protocol doesn't support it, you can check this by
> > looking up your device on ~/.config/kdeconnnect/trusted_devices, the section
> > name is your device-id. if this is the case you need to delete your app data
> > and pair again your device. after that you _might_ upgrade your android
> > version.
> > 
> > 
> > some of this info was taken from github.com/metallkopf/konnect
> 
> For me, clearing storage and cache on KDE Connect on my cellphone fixed the
> issue.

Yep - clearing storage on the Android APP helped also for me - Thanks :)

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

[plasmashell] [Bug 502099] Problems on a global scale. Blurry icons.

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

--- Comment #4 from Nate Graham  ---
Can you attach a screenshot with Breeze icons too, for completeness' sake?

Can you experiment with different scale factors and see if only some cause
blurriness?

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

[plasmashell] [Bug 502099] Problems on a global scale. Blurry icons.

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Nate Graham  ---
Ah never mind, this is just Bug 501944.

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

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

[kwin] [Bug 501944] Low fractional scale factors are still affected by significant blurriness

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

Nate Graham  changed:

   What|Removed |Added

Summary|Some fractional scale   |Low fractional scale
   |factors are still affected  |factors are still affected
   |by significant blurriness   |by significant blurriness
 CC||xaver.h...@gmail.com

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

[kwin] [Bug 501944] Some fractional scale factors are still affected by significant blurriness

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

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #10 from Nate Graham  ---
It looks like the blurriness increases the closer we get to 100%, without
actually being 100%.

To a certain extent this makes sense since 100% will be pixel-perfect, while
anything larger but below 200% will not be pixel perfect. It appears that the
lack of pixel-perfection becomes is more easily hide-able the higher the scale
is.

I wonder how fixable this really is. KWin may have to get extremely clever with
its scaling algorithms for low fractional scales.

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

[kdeconnect] [Bug 501635] KDE Connect: Android 13 and Android 14 cannot search for each other, nor can they be added to the list by IP

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

Eliseu Amaro  changed:

   What|Removed |Added

 CC||holo-...@t-online.de

--- Comment #14 from Eliseu Amaro  ---
*** Bug 502409 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 502489] New: Brush build up mode - issue at low opacity - color never reaches 1005

2025-04-06 Thread Wolfgang Baer

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

Bug ID: 502489
   Summary: Brush build up mode - issue at low opacity - color
never reaches 1005
Classification: Applications
   Product: krita
   Version: 5.2.9
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@cgidesign.de
  Target Milestone: ---

Created attachment 180044
  --> https://bugs.kde.org/attachment.cgi?id=180044&action=edit
Buil up issue in 8bit document

SUMMARY

Tested with Krita 5.2.9 from Krita.org, 5.3 prealpha and 6.0 prealpha (Windows
10) - no pen, only touchpad of the notebook.

krita-artists.org thread:
https://krita-artists.org/t/brush-build-up-mode-issue-at-low-opacity-values/120242

Brush (pixel engine) is set to “Build up” in the settings (all pressure
settings are off). As I understand it, in this mode the “Flow” settings get
ignored (they don’t have an effect) and “Opacity” acts like the “Flow”
parameter.

This mode builds up color in a single stroke if I paint over the same area
multiple times (like with a real pencil on paper where you move it forth and
back without lifting it).

What I expexted:
Regardless of what “Opacity” value I set for the brush, if paint over the same
area often enough I will get 100% color.

But as shown in the screen shot, if the Opacity is at a low level (1% for
example) this does not work. I paint endlessly over the same area but don’t get
to 100%.

Additional information from Freyalupen posted in the above linked thread:

"Checking the color numbers, 16bit integer isn’t perfect either. With pure
green on black I go from 65535 green to 65486. On 8bit it’s 255 to 206.
Interestingly the difference in both cases is 49, suggesting they have the same
problem. On 16bit it’s a visually indistinguishable .07% difference, but on
8bit it’s huge 19% difference."


STEPS TO REPRODUCE
1. Make a new Krita document (in 8bit mode the issue is visually obvious, in
16bit integer it is there as well but not visually perceptible)
2. Set a pixel engine brush to use build up mode
3. Set brush opacity to 1%
4. Paint over the same area multiple times without lifting the brush

OBSERVED RESULT
Color does not get to 100%

EXPECTED RESULT
Color gets to 100%

SOFTWARE/OS VERSIONS
Windows: 10 but happens with other versions as well.

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

[krita] [Bug 502489] Brush build up mode - issue at low opacity - color never reaches 100%

2025-04-06 Thread Wolfgang Baer

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

--- Comment #1 from Wolfgang Baer  ---
Created attachment 180045
  --> https://bugs.kde.org/attachment.cgi?id=180045&action=edit
issue in 8bit and 16bit

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

[plasmashell] [Bug 502480] Plasma 6.3.4 breaks Panel Colorizer

2025-04-06 Thread Luis Bocanegra

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

Luis Bocanegra  changed:

   What|Removed |Added

 CC||luisbocanegra...@gmail.com

--- Comment #2 from Luis Bocanegra  ---
Hi, Panel Colorizer dev here, my widget uses a weird hack with two invisible
rectangles to keep a hold of the Kirigami.Theme colors, but something changed
somewhere and now these invisible rectangles have become black, making them
visible with opacity of 0 seems to get around this change.

If I recall correctly I had to use that approach to avoid overriding the color
bindings or something like that, but maybe there is a better approach I am
unaware of

patch:
https://github.com/luisbocanegra/plasma-panel-colorizer/commit/d167eafe75c2c8cc06b88687ac15130621ff53a2
downstream report:
https://github.com/luisbocanegra/plasma-panel-colorizer/issues/212

Not sure if it still can break due to
https://invent.kde.org/plasma/libplasma/-/commit/f37ea393ff97ec5b8ac66ed33028e5c7b7539659
but it seems it doesn't

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

[plasmashell] [Bug 502065] When in edit mode, keep 'Save" button grayed out until the content is modified

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

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

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

[systemsettings] [Bug 461586] Uninformative notification when I try to set a weak password to wi-fi connection

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

Nate Graham  changed:

   What|Removed |Added

 OS|macOS   |Linux
  Component|kcm_snap|kcm_netpref

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

[systemsettings] [Bug 461586] Uninformative notification when I try to set a weak password to wi-fi connection

2025-04-06 Thread Nicolas Fella

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

Nicolas Fella  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com
  Component|kcm_netpref |kcm_networkmanagement

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

[amarok] [Bug 502490] New: Each applet should get the full context view space (in its own "tab")

2025-04-06 Thread jolay

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

Bug ID: 502490
Summary: Each applet should get the full context view space (in
its own "tab")
Classification: Applications
Product: amarok
Version: 3.2.2
Platform: Flatpak
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Context View
Assignee: amarok-bugs-d...@kde.org
Reporter: jolay...@gmail.com
Target Milestone: kf5

Thank you very much for reviving this great software !
I am now using it daily from flatpak, waiting for it to be in the official
backport repos some day (I am on Debian stable ;-) )

This report is about the usability of the Context View applets in general.
May be the title should be "The Context View should have predictable applet
positions" ? since the user never know where to focus her/his attention after a
mouse click. Sometimes, the applet is half displayed and one needs to scroll up
or down (an extra action).

SUMMARY

Navigating between the applets in the context view is difficult, with multiple
UI "knobs" to act on:
a. the expand(arrow down)/shrink(arrow up-down) buttons for each applet,
b. inner vertical (or horizontal) scrollbar for some applets (ex. Albums and
Wikipedia),
c. outer vertical scrollbar for the context view,
d. and finally, the row of buttons at the bottom, for direct access to each
applet, but they do not expand automatically the applet.

There are many side effects between b. and c. when scrolling with the mouse
wheel button:

- for example, when scrolling with the mouse wheel button in an applet (ex. the
albums), one ends up moving the whole context view stack (c. the outer scroll
bar) unexpectedly if the inner scrollbar (b.) reaches its upper limits.

- and inversely, one can start scrolling (c.), then the action switches to (b.)
unexpectedly because the mouse action is intercepted by the applet that moves
under the mouse pointer.

In some conditions in the Albums applet, expanding to view a (long) album's
track list shift the Context View stack up or down.

As a result, the applets positions on the screen seem unpredictable.

EXPECTED RESULT

1. The applets buttons at the bottom act as navigation tabs. Then, it may be
easier and user-friendly to grant each applet its own full sized context view
(~like in a web browser).

2. This would gives a predictable behaviour, no hazardous scrolling, and may
give rooms to expand and customize the applets views.

3. The UI components (a.) and (c.) would be unnecessary, such as the option to
customize the applet size (I know that it is hidden somewhere, in a place I
could not find :-)

Notes:
-- The "current track" and five "similar artists" fit well in one context view
tab.
-- A tab with only "similar artists" can list more than five (if the user want
to customize it as needed)
-- A tab for "Albums" can show (and edit?) the tracks rating 🟊🟊🟊✩✩, instead of
being a duplicate of filtering the library with the current artist name. As of
now, if the track is not currently playing, the only possibility to view and
edit the rating tag is to open the "Edit Tags" window (right-click on the
selected track(s), one track at a time if the ratings are different)
-- If unmodified, the "Albums" applet is also similar to a simple track menu
action "Show artist" like the menu "Show media source"

SOFTWARE/OS VERSIONS
Amarok: flatpak version, app/org.kde.amarok/x86_64/stable 3.2.2
Linux/KDE Plasma: Debian Bookworm
KDE Frameworks Version: 5.116.0

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 502480] Plasma 6.3.4 breaks Panel Colorizer