[kdeconnect] [Bug 425389] New: Filesystem expose: raw:* and msd:* entries error out on Debian

[user]

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

Bug ID: 425389
   Summary: Filesystem expose: raw:* and msd:* entries error out
on Debian
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Unspecified
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: gwmeeqqhvjyhpan...@ttirv.org
  Target Milestone: ---

On my Samsung Galaxy A21S (stock Android 10, f-droid's KDE Connect 1.14.2),
the "filesystem expose" plugin directories include
- raw:/storage/emulated/0/Download/k
  - Debian fails when trying to create a file or directory in a raw:* dir:
"File already exists".
  - strace mkdir abc
mkdir("abc", 0777) = -1 EEXIST
- msd:19
  - How to create:
Click to add a storage location, choose a dir in the file list that opens,
click the blue button at the bottom to allow access.
  - Debian creates files and dirs in msd:* dirs, however it still prints
an error: "No such file or directory".
  - strace mkdir ghi
mkdir("ghi", 0777) = -1 ENOENT
- primary:Download
  - How to create:
Click to add a storage location, click on the sandwich menu at the left,
choose the internal memory ("Galaxy A21S"), navigate and choose the dir,
click the blue button at the bottom to allow access.
  - Works flawlessly on Debian.

Debian is Debian 10 KDE with no third-party repos and kdeconnect 1.3.3-2.

Additional info:
- All permissions were granted to the app.
- "Share and receive" works, on the same network, between this phone and older
  phones that run older Android versions.
- "Filesystem expose" works, on the same network, between the PC and older
  phones that run older Android versions.
- Other phones with older Android and KDE Connect 1.14.2 only have primary:*
  entries, and they work on Debian.

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

[kontact] [Bug 420052] Cannot create folders in Personal Contacts

[User]

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

--- Comment #2 from User  ---
I can confirm this on Fedora 31 updated yesterday to latest release:
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.68.0
QT Version: 5.13.2

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

[kontact] [Bug 420222] New: Cannot create multiple local address books

[User]

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

Bug ID: 420222
   Summary: Cannot create multiple local address books
   Product: kontact
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: contacts
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@peleion.com
  Target Milestone: ---

SUMMARY

Cannot create multiple local address books, i.e. Personal Contacts, Work
Contacts

STEPS TO REPRODUCE
1. New -> Add address book -> Personal Contacts (type)
2. Enter a new directory (ex: ~/.local/share/contacts-work)
3. Change name of new Address Book (ex: from Personal Contacts to Work
Contacts)

OBSERVED RESULT

- New Address Book name is displayed properly
- Address Book Properties shows correct (separate) directory path
- all vCards are all still stored in ~/.local/share/contacts, does not matter
if new directory existed previous to creation - dialog states "If the directory
does not exist, it will be created"
- Contacts listed are now doubled on name list

EXPECTED RESULT

- vCards actually stored in specified directory (ex:
~/.local/share/contacts-work)
- Able to select/deselect new address book and have contacts list appropriately

SOFTWARE/OS VERSIONS

Linux version: Fedora 31 AMD64 (current)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2

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

[Discover] [Bug 386958] New: Discover crashes after install updates

[user]

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

Bug ID: 386958
   Summary: Discover crashes after install updates
   Product: Discover
   Version: 5.8.8
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: hw...@hi2.in
  Target Milestone: ---

Application: plasma-discover (5.8.8)

Qt Version: 5.7.1
Frameworks Version: 5.40.0
Operating System: Linux 4.10.0-38-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

-- Information about the crash:
- What I was doing when the application crashed:

I was just install new updates. This bug repeats every time.

The crash can be reproduced every time.

-- Backtrace:
Application: Центр приложений Discover (plasma-discover), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe1042a18c0 (LWP 26649))]

Thread 11 (Thread 0x7fe0c13e1700 (LWP 26668)):
#0  0x7fe1017c1d62 in socketNotifierSourceCheck (source=0x7fe0b40013a0) at
kernel/qeventdispatcher_glib.cpp:75
#1  0x7fe0fc3e8dc1 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe0fc3e9330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe0fc3e949c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe1017c275b in QEventDispatcherGlib::processEvents
(this=0x7fe0b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fe10176d0ba in QEventLoop::exec (this=this@entry=0x7fe0c13e0d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7fe10159cf64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7fe1015a1b48 in QThreadPrivate::start (arg=0x2c4e230) at
thread/qthread_unix.cpp:368
#8  0x7fe0fe4d76ba in start_thread (arg=0x7fe0c13e1700) at
pthread_create.c:333
#9  0x7fe100ba53dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fe0c39d8700 (LWP 2)):
#0  0x7ffc711feb0b in clock_gettime ()
#1  0x7fe100bb3836 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7fe0c39d7a70) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fe101647241 in qt_clock_gettime (ts=0x7fe0c39d7a70, clock=) at tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x7fe1017c03d9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7fe0b8001470) at kernel/qtimerinfo_unix.cpp:91
#6  0x7fe1017c0945 in QTimerInfoList::timerWait (this=0x7fe0b8001470,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7fe1017c1fac in timerSourcePrepareHelper (timeout=0x7fe0c39d7b34,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  idleTimerSourcePrepare (source=, timeout=0x7fe0c39d7b34) at
kernel/qeventdispatcher_glib.cpp:212
#9  0x7fe0fc3e891d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fe0fc3e92bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fe0fc3e949c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7fe1017c275b in QEventDispatcherGlib::processEvents
(this=0x7fe0b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7fe10176d0ba in QEventLoop::exec (this=this@entry=0x7fe0c39d7d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#14 0x7fe10159cf64 in QThread::exec (this=) at
thread/qthread.cpp:507
#15 0x7fe1015a1b48 in QThreadPrivate::start (arg=0x292bb50) at
thread/qthread_unix.cpp:368
#16 0x7fe0fe4d76ba in start_thread (arg=0x7fe0c39d8700) at
pthread_create.c:333
#17 0x7fe100ba53dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fe0c8ad0700 (LWP 26660)):
#0  0x7fe100b9970d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe0fc3e938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe0fc3e9712 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe0ca4a89d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7fe0fc40fbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fe0fe4d76ba in start_thread (arg=0x7fe0c8ad0700) at
pthread_create.c:333
#6  0x7fe100ba53dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fe0c92d1700 (LWP 26659)):
#0  0x7fe0fc42da94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fe0fc3e94a6 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe0fc3e94d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe0fc40fbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe0fe4d76ba in start_thread (arg=0x7fe0c92d1700) at
pthread_creat

[KClock] [Bug 464819] New: Text Overlaping

[Kde User]

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

Bug ID: 464819
   Summary: Text Overlaping
Classification: Applications
   Product: KClock
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: espi...@gmail.com
  Reporter: sayige5...@moneyzon.com
CC: hanyo...@protonmail.com
  Target Milestone: ---

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

STEPS TO REPRODUCE
1. Launch Kclock
2. Head Over To Stopwatch Option
3. Start the Timer 
4. Click On Lap 
5. Long Press Enter Key Till it Reach the Count of #999 After that the Text
Starts To Overlap

SOFTWARE/OS VERSIONS
Linux: Arch Linux 
Graphics Platform: X11
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

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

[Powerdevil] [Bug 489163] New: KDE Power Management tray icon crashes when attempting to adjust screen brightness on Plasma 6.1

[KDE User]

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

Bug ID: 489163
   Summary: KDE Power Management tray icon crashes when attempting
to adjust screen brightness on Plasma 6.1
Classification: Plasma
   Product: Powerdevil
   Version: 6.1.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kde.h2...@simplelogin.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

Application: org_kde_powerdevil (6.1.0)

Qt Version: 6.7.1
Frameworks Version: 6.3.0
Operating System: Linux 6.9.6-201.fsync.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40.20240624.0 (Bazzite)"
DrKonqi: 6.1.0 [CoredumpBackend]

-- Information about the crash:
1. Open the screen brightness applet on the system tray
2. Adjust display brightness two times
3. The applet will crash

I am running Bazzite (Fedora based) testing branch with the NVIDIA 555.52.04
driver with KDE Plasma 6.1.0.
I have 3 monitors connected.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Power Management System (org_kde_powerdevil), signal: Aborted


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 7603]
[New LWP 7457]
[New LWP 7608]
[New LWP 7493]
[New LWP 7431]
[New LWP 7459]
[New LWP 7458]
[New LWP 7492]
[New LWP 7609]
[New LWP 7495]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/org_kde_powerdevil'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f905caab144 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f902be006c0 (LWP 7603))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7f902be006c0 (LWP 7603))]

Thread 10 (Thread 0x7f903d4006c0 (LWP 7495)):
#0  0x7f905cb1d75d in poll () from /lib64/libc.so.6
#1  0x7f905b770c34 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f905b714f37 in g_main_loop_run () from /lib64/libglib-2.0.so.0
#3  0x7f90557a0682 in gdbus_shared_thread_func.lto_priv () from
/lib64/libgio-2.0.so.0
#4  0x7f905b73f813 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#5  0x7f905caa91b7 in start_thread () from /lib64/libc.so.6
#6  0x7f905cb2b3cc in clone3 () from /lib64/libc.so.6

Thread 9 (Thread 0x7f90318006c0 (LWP 7609)):
#0  0x7f905cb1d75d in poll () from /lib64/libc.so.6
#1  0x7f905b770c34 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f905b710383 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f905d47cb53 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt6Core.so.6
#4  0x7f905d1a2713 in
QEventLoop::exec(QFlags) () from
/lib64/libQt6Core.so.6
#5  0x7f905d2b414f in QThread::exec() () from /lib64/libQt6Core.so.6
#6  0x7f905d34fc5c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#7  0x7f905caa91b7 in start_thread () from /lib64/libc.so.6
#8  0x7f905cb2b3cc in clone3 () from /lib64/libc.so.6

Thread 8 (Thread 0x7f90452006c0 (LWP 7492)):
#0  0x7f905cb291bd in syscall () from /lib64/libc.so.6
#1  0x7f905b76dccd in g_cond_wait () from /lib64/libglib-2.0.so.0
#2  0x7f905b6d961b in g_async_queue_pop_intern_unlocked () from
/lib64/libglib-2.0.so.0
#3  0x7f905b740a03 in g_thread_pool_spawn_thread () from
/lib64/libglib-2.0.so.0
#4  0x7f905b73f813 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#5  0x7f905caa91b7 in start_thread () from /lib64/libc.so.6
#6  0x7f905cb2b3cc in clone3 () from /lib64/libc.so.6

Thread 7 (Thread 0x7f9046c006c0 (LWP 7458)):
#0  0x7f905cb1d75d in poll () from /lib64/libc.so.6
#1  0x7f905a576dc5 in QtWaylandClient::EventThread::run() () from
/lib64/libQt6WaylandClient.so.6
#2  0x7f905d34fc5c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#3  0x7f905caa91b7 in start_thread () from /lib64/libc.so.6
#4  0x7f905cb2b3cc in clone3 () from /lib64/libc.so.6

Thread 6 (Thread 0x7f90462006c0 (LWP 7459)):
#0  0x7f905cb1d75d in poll () from /lib64/libc.so.6
#1  0x7f905a576dc5 in QtWaylandClient::EventThread::run() () from
/lib64/libQt6WaylandClient.so.6
#2  0x7f905d34fc5c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#3  0x7f905caa91b7 in start_thread () from /lib64/libc.so.6
#4  0x7f905cb2b3cc in clone3 () from /lib64/libc.so.6

Thread 5 (Thread 0x7f9055438400 (LWP 7431)):
#0  0x7f905cb1d75d in poll () from /lib64/libc

[Powerdevil] [Bug 489163] Powerdevil crashes in DDC code when attempting to adjust screen brightness on Plasma 6.1

[KDE User]

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

--- Comment #2 from KDE User  ---
I was able to consistently crash it but now I cannot for whatever reason. I'll
try debugging it tomorrow if I can crash it again.

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

[Powerdevil] [Bug 489163] Powerdevil crashes in DDC code when attempting to adjust screen brightness on Plasma 6.1

[KDE User]

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

--- Comment #3 from KDE User  ---
I am unable to reproduce the bug anymore. Feel free to close this report if no
further action can be taken.

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

[plasma-nm] [Bug 477714] plasma network widget does not connect to open wifi (nmcli works)

[Kubuntu-User]

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

Kubuntu-User  changed:

   What|Removed |Added

 CC||no...@vollbio.de

--- Comment #1 from Kubuntu-User  ---
The issue is still valid at April 2024 - It happens also with unecrypted wifi
wlan networks like freifunk.
(securoty type = none)

Apr 17 12:27:07 workstation NetworkManager[900]:   [1713349627.9540]
audit: op="connection-add-activate" pid=1776 uid=1000 result="fail"
reason="802-11-wireless-security.key-mgmt: Access point does not support PSK
but setting requires it"
Apr 17 12:27:15 workstation NetworkManager[900]:   [1713349635.4389]
audit: op="connection-add-activate" pid=1776 uid=1000 result="fail"
reason="802-11-wireless-security.key-mgmt: Access point does not support PSK
but setting requires it"
Apr 17 12:27:26 workstation NetworkManager[900]:   [1713349646.4014]
audit: op="connection-add-activate" pid=1776 uid=1000 result="fail"
reason="802-11-wireless-security.key-mgmt: Access point does not support PSK
but setting requires it"

The only workaround is currently:

root@bash# nmcli device wifi connect ffm.freifunk.net
Device 'wlp58s0' successfully activated with
'db621853-0c04-4c5c-b31a-ba54b44cfb02'.

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

[systemsettings] [Bug 486499] New: Cannot connect to open WLAN (OWE) with Kubuntu | 802-11-wireless-security.key-mgmt: Access point does not support PSK but setting requires it

[Kubuntu-User]

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

Bug ID: 486499
   Summary: Cannot connect to open WLAN (OWE) with Kubuntu |
802-11-wireless-security.key-mgmt: Access point does
not support PSK but setting requires it
Classification: Applications
   Product: systemsettings
   Version: 5.24.6
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_networkmanagement
  Assignee: plasma-b...@kde.org
  Reporter: no...@vollbio.de
CC: jgrul...@redhat.com
  Target Milestone: ---

SUMMARY

If I would like connect on my Kubuntu 24.04 to a open Wifi with OWE like
ffm.freifunk.net, then I am unable to connect and I receive a error message in
/var/log/syslog:
"802-11-wireless-security.key-mgmt: Access point does not support PSK but
setting requires it"

Additional hint - the issue occurs with owe networks
(https://en.wikipedia.org/wiki/Opportunistic_Wireless_Encryption)


STEPS TO REPRODUCE
1. Setup a Wifi Device with OWE, for example flash a device with freifunk.net
OpenWRT Firmware: https://firmware.m.net/
2. Watch available Wifi networks
3. "Connect" with free owe network

OBSERVED RESULT

Logmessages:
Apr 17 12:27:02 workstation NetworkManager[900]:  [1713349622.6890]
audit: op="statistics" interface="wlp58s0" ifindex=2 args="0" pid=1776 uid=1000
result="success"
Apr 17 12:27:04 workstation NetworkManager[900]:  [1713349624.3895]
audit: op="statistics" interface="wlp58s0" ifindex=2 args="2000" pid=1776
uid=1000 result="success"
Apr 17 12:27:07 workstation NetworkManager[900]:  [1713349627.9540]
audit: op="connection-add-activate" pid=1776 uid=1000 result="fail"
reason="802-11-wireless-security.key-mgmt: Access point does not support PSK
but setting requires it"
Apr 17 12:27:15 workstation NetworkManager[900]:  [1713349635.4389]
audit: op="connection-add-activate" pid=1776 uid=1000 result="fail"
reason="802-11-wireless-security.key-mgmt: Access point does not support PSK
but setting requires it"
Apr 17 12:27:26 workstation NetworkManager[900]:  [1713349646.4014]
audit: op="connection-add-activate" pid=1776 uid=1000 result="fail"
reason="802-11-wireless-security.key-mgmt: Access point does not support PSK
but setting requires it"
Apr 17 12:27:32 workstation NetworkManager[900]:  [1713349652.2236]
audit: op="connection-add-activate" pid=1776 uid=1000 result="fail"
reason="802-11-wireless-security.key-mgmt: Access point does not support PSK
but setting requires it"

The wifi data of ffm.freifunk.net:


bash$ nmcli dev wifi 
IN-USE  BSSID  SSID MODE   CHAN  RATE   
SIGNAL  BARS  SECURITY  
DE:83:89:1B:D6:A8  ffm.freifunk.net Infra  1 130 Mbit/s  90
 ▂▄▆█  OWE   
DE:83:89:1B:D6:AA  owe.ffm.freifunk.net Infra  1 130 Mbit/s  90
 ▂▄▆█  OWE   



EXPECTED RESULT

The open wifi with OWE should get an connection.

The workaround ist curently this:
root@bash# nmcli device wifi connect ffm.freifunk.net
Device 'wlp58s0' successfully activated with 'db.2'.




SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubunti 24.04
(available in About System)
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Last updates are applied. 2024/05/03

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

[systemsettings] [Bug 486499] Cannot connect to open WLAN (OWE) with Kubuntu | 802-11-wireless-security.key-mgmt: Access point does not support PSK but setting requires it

[Kubuntu-User]

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

Kubuntu-User  changed:

   What|Removed |Added

   Platform|Other   |Kubuntu

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

[systemsettings] [Bug 486499] Cannot connect to open WLAN (OWE) with Kubuntu | 802-11-wireless-security.key-mgmt: Access point does not support PSK but setting requires it

[Kubuntu-User]

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

--- Comment #1 from Kubuntu-User  ---
Created attachment 169131
  --> https://bugs.kde.org/attachment.cgi?id=169131&action=edit
Wifi scan data for affected open wifi network with owe

Here a scan of the affected open wifi with OWE ffm.freifunk.net

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

[systemsettings] [Bug 486499] Cannot connect to open WLAN (OWE) with Kubuntu | 802-11-wireless-security.key-mgmt: Access point does not support PSK but setting requires it

[Kubuntu-User]

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

Kubuntu-User  changed:

   What|Removed |Added

 CC||no...@vollbio.de

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

[ksplash] [Bug 432321] New: ksplashqml PID: 2046 Signal: Segmentation fault

[Fedora User]

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

Bug ID: 432321
   Summary: ksplashqml PID: 2046 Signal: Segmentation fault
   Product: ksplash
   Version: 5.9.1
  Platform: Fedora RPMs
OS: Microsoft Windows
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: fedorarpmcrea...@gmail.com
  Target Milestone: ---

Created attachment 135312
  --> https://bugs.kde.org/attachment.cgi?id=135312&action=edit
Screen-shot-error-output

SUMMARY
On/around Jan 24 2021 after updating of approximately 154 packages
I get a black screen with ksplashqml crash window.
Recovery is to roll back per snapshot.


STEPS TO REPRODUCE
1. Install updates
2. Reboot
3. Login 

OBSERVED RESULT
Black screen

EXPECTED RESULT
Normal desktop view

SOFTWARE/OS VERSIONS
Windows: 10 Pro
Oracle Virtual Box: 6.1.16r140961 (QT5.6.2)
Fedora 33 Mate-Compiz
Linux/KDE Plasma:5.20.5
(available in About System)
KDE Plasma Version: Plasma:5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version 5.9.16-200.fc33.x86_64

ADDITIONAL INFORMATION
On/around Jan 24 2021 after updating of approximately 154 packages
I get a black screen with ksplashqml crash window.
Recovery is to roll back per snapshot.

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

[ksplash] [Bug 432321] ksplashqml PID: 2046 Signal: Segmentation fault

[Fedora User]

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

--- Comment #2 from Fedora User  ---
This is my first bug submission so bear with me.
How do I collect the back trace?

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

[ksplash] [Bug 432321] ksplashqml PID: 2046 Signal: Segmentation fault

[Fedora User]

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

--- Comment #5 from Fedora User  ---
Yes I've rebooted. After reboot I get the black screen with the 
ksplashqml PID error. What package effects ksplashqml?
Maybe I can exclude the problem package.

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

[ksplash] [Bug 432321] ksplashqml PID: 2046 Signal: Segmentation fault

[Fedora User]

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

--- Comment #6 from Fedora User  ---
Created attachment 135403
  --> https://bugs.kde.org/attachment.cgi?id=135403&action=edit
DNF Updated List

DNF Updated List

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

[ksplash] [Bug 432321] ksplashqml PID: 2046 Signal: Segmentation fault

[Fedora User]

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

--- Comment #7 from Fedora User  ---
Here's the newest crash info for this issue. Now with kernel 5.10 I'm getting
exit error.
Executable: ksmserver-logout-greeter PID: 109120 Signal: Segmentation fault
(11) Time: 2/3/21 6:18:48 PM PST

[KCrash Handler]
#4 0x in ?? ()
#5 0x7f3e5ac6eb42 in QGLXContext::makeCurrent(QPlatformSurface*) () from
/usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#6 0x7f3e6df626ee in QOpenGLContext::makeCurrent(QSurface*) () from
/lib64/libQt5Gui.so.5
#7 0x7f3e6f277f56 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5
#8 0x7f3e6d952df0 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9 0x7f3e6c5353f9 in start_thread () from /lib64/libpthread.so.0
#10 0x7f3e6d5ba903 in clone () from /lib64/libc.so.6


Thread 4 (Thread 0x7f3e52fff640 (LWP 109125) "QQmlThread"):
#1 0x7f3e6bc426f6 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#2 0x7f3e6bbedd43 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3 0x7f3e6db3a70b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4 0x7f3e6daec57b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5 0x7f3e6d951b67 in QThread::exec() () from /lib64/libQt5Core.so.5
#6 0x7f3e6eed55ec in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5
#7 0x7f3e6d952df0 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8 0x7f3e6c5353f9 in start_thread () from /lib64/libpthread.so.0
#9 0x7f3e6d5ba903 in clone () from /lib64/libc.so.6


Thread 3 (Thread 0x7f3e5ac4d640 (LWP 109122) "QDBusConnection"):
#1 0x7f3e6bc426f6 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#2 0x7f3e6bbedd43 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3 0x7f3e6db3a70b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4 0x7f3e6daec57b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5 0x7f3e6d951b67 in QThread::exec() () from /lib64/libQt5Core.so.5
#6 0x7f3e6eadf10b in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#7 0x7f3e6d952df0 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8 0x7f3e6c5353f9 in start_thread () from /lib64/libpthread.so.0
#9 0x7f3e6d5ba903 in clone () from /lib64/libc.so.6


Thread 2 (Thread 0x7f3e5b75c640 (LWP 109121) "QXcbEventQueue"):
#1 0x7f3e6d1c2842 in _xcb_conn_wait.part.0 () from /lib64/libxcb.so.1
#2 0x7f3e6d1c41cc in xcb_wait_for_event () from /lib64/libxcb.so.1
#3 0x7f3e5b866448 in QXcbEventQueue::run() () from /lib64/libQt5XcbQpa.so.5
#4 0x7f3e6d952df0 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5 0x7f3e6c5353f9 in start_thread () from /lib64/libpthread.so.0
#6 0x7f3e6d5ba903 in clone () from /lib64/libc.so.6


Thread 1 (Thread 0x7f3e68e87980 (LWP 109120) "ksmserver-logou"):
#1 0x7f3e6d9589bb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt5Core.so.5
#2 0x7f3e6f273426 in
QSGThreadedRenderLoop::polishAndSync(QSGThreadedRenderLoop::Window*, bool) ()
from /lib64/libQt5Quick.so.5
#3 0x7f3e6f278a39 in QSGThreadedRenderLoop::exposureChanged(QQuickWindow*)
() from /lib64/libQt5Quick.so.5
#4 0x7f3e6df347b5 in QWindow::event(QEvent*) () from /lib64/libQt5Gui.so.5
#5 0x7f3e6e582ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#6 0x7f3e6daedbd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#7 0x7f3e6df2a7d5 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() from /lib64/libQt5Gui.so.5
#8 0x7f3e6df0a8cc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib64/libQt5Gui.so.5
#9 0x7f3e5b86747e in xcbSourceDispatch(_GSource*, int (*)(void*), void*) ()
from /lib64/libQt5XcbQpa.so.5
#10 0x7f3e6bbf096f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#11 0x7f3e6bc42758 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#12 0x7f3e6bbedd43 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#13 0x7f3e6db3a6f3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#14 0x7f3e6daec57b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#15 0x7f3e6daf41b4 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#16 0x561b90bf19e9 in main ()
[Inferior 1 (process 109120) detached]

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

[ksplash] [Bug 432321] ksplashqml PID: 2046 Signal: Segmentation fault

[Fedora User]

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

--- Comment #8 from Fedora User  ---
I'm also still getting the Executable: ksplashqml PID: 2046 Signal:
Segmentation fault error after reboot today.

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

[ksplash] [Bug 432321] ksplashqml PID: 2046 Signal: Segmentation fault

[Fedora User]

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

Fedora User  changed:

   What|Removed |Added

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

--- Comment #9 from Fedora User  ---
(In reply to Fedora User from comment #8)
> I'm also still getting the Executable: ksplashqml PID: 2046 Signal:
> Segmentation fault error after reboot today.

You can close this bug.
I spun up another VM for Fedora 33 installed updates with no issues.

This bug/issue is generated from the problem VM Fedora 33 upgraded from fedora
33.
I also installed a theme, I can't remember which one. Thanks for looking at
this.

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

[plasmashell] [Bug 486655] Panel/dock set to fit content, align center, floating and auto-hiding will start up being too long in Wayland

[KDE User]

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

KDE User  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from KDE User  ---
I no longer encounter this issue. Unsure when this was resolved since I only
recently moved back into Wayland after several updates. Marking as resolved.

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

[kscreenlocker] [Bug 489846] Lock screen freezes when waking monitor from power saving mode, takes ~10-20 seconds to respond (X11 only)

[KDE User]

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

KDE User  changed:

   What|Removed |Added

 CC||kde.h2...@simplelogin.com

--- Comment #4 from KDE User  ---
I have the same issue on Bazzite with KDE Plasma 6.1.1. Using an NVIDIA card
3060ti driver: 555.58.02.

A quick (but possible insecure) workaround is to drop into a tty (ALT+F3) and
type in:

```
sudo loginctl unlock-sessions
```

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

[kdeconnect] [Bug 401140] On Pixel 3, incoming calls are reported as Unknown Number

[Xiaomi user]

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

--- Comment #1 from Xiaomi user  ---
Same situation on Xiaomi A2 Lite (Android 9).

PC side tested on :
- Solus GNOME 3. with GSConnect 17
- KDE Neon 5.14.5 with KDE Connect 1.3.3

Android side tested with KDE Connect versions :
- 1.10.1
- 1.7.1
- 1.6.6

Debug log of GSConnect reveal that none of above app version does not send
contact name nor phone number in packet sent to PC, when there's incoming call
:

DEBUG: [core.js:receive/<:404]: xiaomi: {
  "id": 1547125458472,
  "type": "kdeconnect.telephony",
  "body": {
"event": "ringing"
  }
}

while it should looks like :

DEBUG: [core.js:receive/<:404]: Samsung SM-A310F: {
  "id": 1547126528778,
  "type": "kdeconnect.telephony",
  "body": {
"contactName": "Test number",
"phoneNumber": "555666777",
"event": "ringing"
  }
}

Also for outgoing call there is no info about contact :

DEBUG: [core.js:receive/<:404]: xiaomi: {
  "id": 1547126522752,
  "type": "kdeconnect.telephony",
  "body": {
"event": "talking"
  }
}

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

[kdeconnect] [Bug 401140] On Pixel 3, incoming calls are reported as Unknown Number

[Xiaomi user]

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

Xiaomi user  changed:

   What|Removed |Added

 OS|Linux   |Android 9.x
   Platform|Other   |Android

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

[kwordquiz] [Bug 401474] New: Cannot create new entires

[DISGRUNTLED USER]

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

Bug ID: 401474
   Summary: Cannot create new entires
   Product: kwordquiz
   Version: 0.9.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: pe...@peterandlinda.com
  Reporter: robert.w.mcc...@gmail.com
  Target Milestone: ---

SUMMARY
Cannot insert new rows into a quiz.
The entire program is fucked and should be deleted from existence.

STEPS TO REPRODUCE
1. Create new file
2. Insert rows
3. Create data
4. Save
5. Reopen with only first 20 rows remembered, even though they exist in the
fucking file.

OBSERVED RESULT
IT DOESN'T FUCKING WORK!

EXPECTED RESULT
IT SHOULD FUCKING WORK!

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

ADDITIONAL INFORMATION

You should not be developing software. You should not claim that this software
is worth a shit. You should not claim to be able to write software. You should
apologize to the entire world for your horrendous lack of trying to actually
test this software.

I hope you do not claim to be a software developer.

You are a shame to open source.

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

[kwin] [Bug 494262] Main monitor is black with cursor and windows visible after unlocking

[KDE User]

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

KDE User  changed:

   What|Removed |Added

Version|6.1.5   |6.2.0

--- Comment #1 from KDE User  ---
6.2.0 has this issue too.

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

[kwin] [Bug 494262] New: Main monitor is black with cursor and windows visible after unlocking

[KDE User]

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

Bug ID: 494262
   Summary: Main monitor is black with cursor and windows visible
after unlocking
Classification: Plasma
   Product: kwin
   Version: 6.1.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kde.h2...@simplelogin.com
  Target Milestone: ---

SUMMARY

I've recently been experiencing an issue where KDE Plasma will unlock into my
main monitor being a black screen while still being able to drag windows into
it and my cursor being visible. My panels will have shifted to another monitor
which still has its wallpaper visible.

I managed to consistently reproduce this issue by starting a fresh Plasma login
session by logging out and logging back in or rebooting. Then locking the
screen and waiting for my main monitor to enter standby mode after 20 seconds -
this is how I have it configured in the Power Management settings. I then wake
it up and login in on the lock screen.

**NOTE**: This issue does not appear if I wake up my main monitor BEFORE it
enters standby mode.

I observe the following log messages that are unique to the issue:

```
Oct 08 07:15:59 bazzite kwin_wayland[12512]: kwin_core:
KWin::LayerShellV1Window doesn't support setting maximized state
Oct 08 07:15:59 bazzite kwin_wayland[12512]: kwin_core:
KWin::LayerShellV1Window doesn't support setting fullscreen state
Oct 08 07:15:59 bazzite kwin_wayland[12512]: kwin_core:
KWin::LayerShellV1Window doesn't support setting maximized state
Oct 08 07:15:59 bazzite kwin_wayland[12512]: kwin_core:
KWin::LayerShellV1Window doesn't support setting fullscreen state
```

These messages do not appear if I wake up my monitor before it enters stand-by
mode so I suspect they must be related to the issue.

STEPS TO REPRODUCE
1. Enter a fresh Plasma Wayland session
2. Lock your screen
3. Wait for your monitors to enter stand-by mode (low power consumption)
4. Wake up your monitors
5. Log in

OBSERVED RESULT

A black background on the main monitor with cursor and windows visible if moved
into it. Panels moved to another monitor.

EXPECTED RESULT

My wallpaper and panels to be visible on the main monitor.

SOFTWARE/OS VERSIONS
Operating System: Bazzite 40
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.9.12-205.fsync.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2

ADDITIONAL INFORMATION

I am aware of https://bugs.kde.org/show_bug.cgi?id=489180 however, I do not
seem to get any log messages relating to
QtWaylandClient::QWaylandWindow::waylandScreen. Also, Plasma doesn't seem to
crash, or if it does, it seems to recover.

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

[kdeconnect] [Bug 493958] Crash on android. After update it fully crash

[kde-user]

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

kde-user  changed:

   What|Removed |Added

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

--- Comment #9 from kde-user  ---
this issue is not fixed

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

[kdeconnect] [Bug 493958] Crash on android. After update it fully crash

[kde-user]

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

kde-user  changed:

   What|Removed |Added

 CC||wdoona...@gmail.com

--- Comment #6 from kde-user  ---
I'm experiencing the same issue.
Three dif android devices, two had auto-updated and kdeconnect crashes when
trying to open.
Using f-droid one device was able to install v1.32.2 and it seems to work OK
Another device received v1.32.3 also using f-droid and it crashes
v1.32.4 from google play also crashes
With 1.32.3 and 1.32.4 the app will function just enough to pair another device
but the moment the pair is accepted the app will crash and not open again.

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

[kwin] [Bug 494262] Main monitor is black with cursor and windows visible after unlocking

[KDE User]

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

--- Comment #2 from KDE User  ---
The issue is still present in QT 6.8.0. Which I think rules out the original QT
issue I highlighted earlier since I _believe_ the patch for that has been
merged into 6.8.0 at the very latest.

Here's an updated info about my system.

Operating System: Bazzite 41
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-307.bazzite.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H WIFI

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

[plasmashell] [Bug 494262] One monitor of a multi-monitor setup is black with cursor and windows visible (its containment has gotten lost) after unlocking

[KDE User]

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

--- Comment #4 from KDE User  ---
(In reply to Nate Graham from comment #3)
> Does the issue go away if you...
> 1. Switch to another TTY and then back?
> 2. Uninstall powerdevil and reboot?

Switching to a TTY didn't resolve it.

I don't think I can remove powerdevil or at least I'm not sure how to do it on
Bazzite.

```
> rpm-ostree override remove powerdevil
Inactive requests:
  fish (already provided by fish-3.7.0-4.fc41.x86_64)
  langpacks-en (already provided by langpacks-en-4.1-2.fc41.noarch)
Checking out tree 0cb7752... done
Resolving dependencies... done
error: Could not depsolve transaction; 1 problem detected:
 Problem: package plasma-workspace-6.2.2-2.fc41.x86_64 from @System requires
powerdevil, but none of the providers can be installed
  - conflicting requests
```

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

[plasmashell] [Bug 494262] One monitor of a multi-monitor setup is black with cursor and windows visible (its containment has gotten lost) after unlocking

[KDE User]

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

--- Comment #8 from KDE User  ---
Here's something. I found a temporary solution which was to disable DDC/CI
support in PowerDevil through the environment variable POWERDEVIL_NO_DDCUTIL.

I thought I would try it because I was running into issues with some of my
monitors not responding to the display brightness applet and repeated attempts
to query the monitor using ddcutil. I figured there's either something wrong
with the implementation of dccutil or there's something wrong with my monitor's
firmware (I suspect the latter).

Disabling ddcutil obviously has the drawback of not being able to control my
display brightness for any display - including those that did work with
properly before. However, I think it's an acceptable compromise for now. It
does indicate that the issue I was experiencing in this ticket is very much
related to DDC/CI or how PowerDevil uses it.

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

[kwin] [Bug 497113] Kwin wayland crashed randomly while fullscreen video was playing

[test user]

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

--- Comment #4 from test user  ---
I do not thing this is really a duplicate, and even if it were the "fix", IMHO
is not a fix.

I didn't update kwin (or any qt package) in recent days and I've 5 days uptime.
The 24h repeated crash doesn't apply. It never happened before either (with
much longer uptime). Also I didn't have the said crash again till now.

The issue in the possible duplicate was tracked down to krunner unit converter
runner. But it is unclear how something running in krunner process (and cgroup)
can trigger a crash for kwin.

I'll try to dig the coredumps next week and if required I'll reopen this or the
possible duplicate one for your comments on findings (if any).

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

[kwin] [Bug 497113] Kwin wayland crashed randomly while fullscreen video was playing

[test user]

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

--- Comment #6 from test user  ---
I just realized. Thanks!

I searched specifically currency conversions in overview right now to start the
timer anyway. I am not updating. If it crashes before this time tomorrow it'll
give peace of mind that the issue is fixed. Thankfully kate, konsole and
browsers (with session restore) survives so I'll not loose work.

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

[plasmashell] [Bug 494262] One monitor of a multi-monitor setup is black with cursor and windows visible (its containment has gotten lost) after unlocking

[KDE User]

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

--- Comment #9 from KDE User  ---
Adding another update. I've started to see the problem recurring again even
with DDC turned off in PowerDevil.

Operating System: Bazzite 41
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-305.bazzite.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H WIFI

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

[kwin] [Bug 497113] Kwin wayland crashed randomly while fullscreen video was playing

[test user]

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

--- Comment #2 from test user  ---
Excat package version for debugging if required.

kwin-wayland-6.1.4-1.fc40.x86_64
systemd-libs-255.10-3.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
kf6-ksvg-6.5.0-1.fc40.x86_64
kf6-kconfigwidgets-6.5.0-1.fc40.x86_64
qaccessibilityclient-qt6-0.6.0-1.fc40.x86_64
kwin-libs-6.1.4-1.fc40.x86_64
kf6-kcrash-6.5.0-1.fc40.x86_64
libepoxy-1.5.10-6.fc40.x86_64
kdecoration-6.1.4-1.fc40.x86_64
qt6-qtdeclarative-6.7.2-2.fc40.x86_64
qt6-qtdeclarative-6.7.2-2.fc40.x86_64
kf6-knotifications-6.5.0-1.fc40.x86_64
kf6-kconfig-6.5.0-1.fc40.x86_64
kf6-kidletime-6.5.0-1.fc40.x86_64
kf6-ki18n-6.5.0-1.fc40.x86_64
kglobalacceld-6.1.4-1.fc40.x86_64
kf6-kwindowsystem-6.5.0-1.fc40.x86_64
kf6-kglobalaccel-6.5.0-1.fc40.x86_64
qt6-qtbase-gui-6.7.2-4.fc40.x86_64
kf6-kservice-6.5.0-1.fc40.x86_64
kf6-kconfig-6.5.0-1.fc40.x86_64
kf6-kcoreaddons-6.5.0-1.fc40.x86_64
qt6-qtbase-6.7.2-4.fc40.x86_64
qt6-qtbase-gui-6.7.2-4.fc40.x86_64
qt6-qtbase-6.7.2-4.fc40.x86_64
libstdc++-14.2.1-1.fc40.x86_64
glibc-2.39-22.fc40.x86_64
glibc-2.39-22.fc40.x86_64
libcap-2.69-8.fc40.x86_64
lz4-libs-1.9.4-6.fc40.x86_64
xz-libs-5.4.6-3.fc40.x86_64
libzstd-1.5.6-1.fc40.x86_64
libgcc-14.2.1-1.fc40.x86_64
libXau-1.0.11-6.fc40.x86_64
qt6-qtsvg-6.7.2-1.fc40.x86_64
kf6-karchive-6.5.0-1.fc40.x86_64
kf6-kcolorscheme-6.5.0-1.fc40.x86_64
kf6-kguiaddons-6.5.0-1.fc40.x86_64
kf6-kwidgetsaddons-6.5.0-1.fc40.x86_64
kf6-kcodecs-6.5.0-1.fc40.x86_64
libwayland-server-1.23.0-2.fc40.x86_64
kf6-kconfig-6.5.0-1.fc40.x86_64
kdecoration-6.1.4-1.fc40.x86_64
systemd-libs-255.10-3.fc40.x86_64
libxkbcommon-1.6.0-2.fc40.x86_64
lcms2-2.16-3.fc40.x86_64
xcb-util-cursor-0.1.4-4.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
xcb-util-wm-0.4.2-5.fc40.x86_64
xcb-util-keysyms-0.4.1-5.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libdrm-2.4.122-1.fc40.x86_64
mesa-libgbm-24.1.5-2.fc40.x86_64
libinput-1.26.1-1.fc40.x86_64
kwayland-6.1.4-1.fc40.x86_64
libwayland-client-1.23.0-2.fc40.x86_64
libX11-xcb-1.8.10-1.fc40.x86_64
libX11-1.8.10-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libXi-1.8.1-5.fc40.x86_64
plasma-activities-6.1.4-1.fc40.x86_64
kscreenlocker-6.1.4-1.fc40.x86_64
qt6-qtsensors-6.7.2-1.fc40.x86_64
qt6-qtbase-gui-6.7.2-4.fc40.x86_64
libdisplay-info-0.1.1-4.fc40.x86_64
libxcvt-0.1.2-6.fc40.x86_64
kf6-kpackage-6.5.0-1.fc40.x86_64
qt6-qtdeclarative-6.7.2-2.fc40.x86_64
qt6-qtbase-6.7.2-4.fc40.x86_64
libcanberra-0.30-35.fc40.x86_64
kf6-kio-gui-6.7.0-1.fc40.x86_64
kf6-kjobwidgets-6.7.0-1.fc40.x86_64
kf6-kio-core-libs-6.7.0-1.fc40.x86_64
libxcb-1.17.0-1.fc40.x86_64
libXfixes-6.0.1-3.fc40.x86_64
qt6-qtbase-6.7.2-4.fc40.x86_64
dbus-libs-1.14.10-3.fc40.x86_64
libglvnd-egl-1.7.0-4.fc40.x86_64
fontconfig-2.15.0-6.fc40.x86_64
glib2-2.80.3-1.fc40.x86_64
libglvnd-glx-1.7.0-4.fc40.x86_64
libglvnd-opengl-1.7.0-4.fc40.x86_64
libpng-1.6.40-3.fc40.x86_64
harfbuzz-8.5.0-1.fc40.x86_64
freetype-2.13.2-5.fc40.x86_64
zlib-ng-compat-2.1.7-1.fc40.x86_64
libicu-74.2-1.fc40.x86_64
libicu-74.2-1.fc40.x86_64
double-conversion-3.3.0-3.fc40.x86_64
libb2-0.98.1-11.fc40.x86_64
pcre2-utf16-10.44-1.fc40.x86_64
openssl-libs-3.2.1-2.fc40.x86_64
bzip2-libs-1.0.8-18.fc40.x86_64
qt6-qtwayland-6.7.2-4.fc40.x86_64
libffi-3.4.4-7.fc40.x86_64
xcb-util-renderutil-0.3.10-5.fc40.x86_64
xcb-util-image-0.4.1-5.fc40.x86_64
expat-2.6.2-1.fc40.x86_64
mtdev-1.1.6-8.fc40.x86_64
libevdev-1.13.2-2.fc40.x86_64
libwacom-2.11.0-1.fc40.x86_64
libXext-1.3.6-1.fc40.x86_64
kf6-kxmlgui-6.7.0-1.fc40.x86_64
krb5-libs-1.21.3-1.fc40.x86_64
libbrotli-1.1.0-3.fc40.x86_64
libproxy-0.5.5-1.fc40.x86_64
libvorbis-1.3.7-10.fc40.x86_64
libtdb-1.4.10-1.fc40.x86_64
libtool-ltdl-2.4.7-10.fc40.x86_64
kf6-solid-6.7.0-1.fc40.x86_64
kf6-kauth-6.5.0-1.fc40.x86_64
libacl-2.3.2-1.fc40.x86_64
libmount-2.40.1-1.fc40.x86_64
libglvnd-1.7.0-4.fc40.x86_64
libxml2-2.12.8-1.fc40.x86_64
pcre2-10.44-1.fc40.x86_64
graphite2-1.3.14-15.fc40.x86_64
libicu-74.2-1.fc40.x86_64
libgomp-14.2.1-1.fc40.x86_64
libwayland-cursor-1.23.0-2.fc40.x86_64
xcb-util-0.4.1-5.fc40.x86_64
libgudev-238-5.fc40.x86_64
glib2-2.80.3-1.fc40.x86_64
qt6-qtbase-gui-6.7.2-4.fc40.x86_64
kf6-kitemviews-6.7.0-1.fc40.x86_64
kf6-kiconthemes-6.5.0-1.fc40.x86_64
kf6-kiconthemes-6.5.0-1.fc40.x86_64
krb5-libs-1.21.3-1.fc40.x86_64
krb5-libs-1.21.3-1.fc40.x86_64
libcom_err-1.47.0-5.fc40.x86_64
krb5-libs-1.21.3-1.fc40.x86_64
keyutils-libs-1.6.3-3.fc40.x86_64
glibc-2.39-22.fc40.x86_64
libbrotli-1.1.0-3.fc40.x86_64
libproxy-0.5.5-1.fc40.x86_64
libvorbis-1.3.7-10.fc40.x86_64
libogg-1.3.5-8.fc40.x86_64
libimobiledevice-1.3.0^20230705git6fc41f5-4.fc40.x86_64
libplist-2.3.0-4.fc40.x86_64
libattr-2.5.2-3.fc40.x86_64
libblkid-2.40.1-1.fc40.x86_64
libselinux-3.6-4.fc40.x86_64
kf6-breeze-icons-6.5.0-1.fc40.x86_64
libcurl-8.6.0-10.fc40

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

[KDE User]

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

KDE User  changed:

   What|Removed |Added

 CC||kde.h2...@simplelogin.com

--- Comment #17 from KDE User  ---
Possible duplicate of https://bugs.kde.org/show_bug.cgi?id=494262 ??

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

[plasmashell] [Bug 494262] One monitor of a multi-monitor setup is black with cursor and windows visible (its containment has gotten lost) after unlocking

[KDE User]

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

--- Comment #6 from KDE User  ---
(In reply to Nate Graham from comment #5)
> Ok, in that case you can temporarily stop and disable its systemd service
> with:
> 
> > sudo systemctl stop plasma-powerdevil.service
> > sudo systemctl disable plasma-powerdevil.service
> 
> Then restart, then see if it still happens.
> 
> To re-enable powerdevil after this testing, do this:
> 
> > sudo systemctl start plasma-powerdevil.service
> > sudo systemctl enable plasma-powerdevil.service

It looks like for my system, the plasma-powerdevil.service is a user service
and cannot be disabled because it doesn't have the `[Install]` field defined
(?) I can stop it however. And after doing so I locked my screen and found that
my monitors don't go to sleep. I'm guessing that feature was handled by
powerdevil to begin with. So in this case does that mean powerdevil has a bug?

Here's the log output of powerdevil for the current boot which did exhibit the
black screen when it was on.

```
Nov 23 17:24:04 bazzite systemd[2140]: Starting plasma-powerdevil.service -
Powerdevil...
Nov 23 17:24:04 bazzite org_kde_powerdevil[2744]: Initializing libddcutil. 
ddcutil version: 2.1.2, shared library: /usr/lib64/libddcutil.so.5.1.1
Nov 23 17:24:04 bazzite org_kde_powerdevil[2744]: Options passed from client:
Nov 23 17:24:04 bazzite org_kde_powerdevil[2744]: Applying combined options:
Nov 23 17:24:04 bazzite org_kde_powerdevil[2744]: busno=2, sleep-multiplier = 
2.00. Testing for supported feature 0x10 returned Error_Info[EIO in
ddc_write_read_with_retry, causes: EIO]
Nov 23 17:24:09 bazzite org_kde_powerdevil[2744]: Library initialization
complete.
Nov 23 17:24:09 bazzite org_kde_powerdevil[2744]: Watch thread started
Nov 23 17:24:11 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
[DDCutilDisplay]: ddca_get_non_table_vcp_value -3007
Nov 23 17:24:11 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
[DDCutilDetector]: Display "ASUS VC239" does not seem to support brightness
control - wait before retrying initialization
Nov 23 17:24:11 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
[DDCutilDisplay]: "ASUS VC239" retrying to initialize DDC/CI brightness in 1000
milliseconds - attempt no. 1
Nov 23 17:24:13 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
[DDCutilDisplay]: "ASUS VC239" succeeded to initialize DDC/CI brightness
Nov 23 17:24:13 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds
are not supported by the kernel for this hardware"
Nov 23 17:24:13 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
org.kde.powerdevil.backlighthelper.brightness failed
Nov 23 17:24:14 bazzite systemd[2140]: Started plasma-powerdevil.service -
Powerdevil.
Nov 23 17:24:14 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil: Handle
button events action could not check for screen configuration
Nov 23 17:24:14 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds
are not supported by the kernel for this hardware"
Nov 23 17:24:17 bazzite org_kde_powerdevil[2744]: dh=Display_Handle[i2c-3:
fd=52], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or
SE_POST_SAVE_SETTINGS
Nov 23 17:41:29 bazzite org_kde_powerdevil[2744]: dh=Display_Handle[i2c-5:
fd=52], Keeping adjusted sleep multiplier 2.00 for SE_POST_WRITE or
SE_POST_SAVE_SETTINGS
Nov 23 17:41:29 bazzite org_kde_powerdevil[2744]: dh=Display_Handle[i2c-3:
fd=52], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or
SE_POST_SAVE_SETTINGS
Nov 23 17:41:30 bazzite org_kde_powerdevil[2744]: dh=Display_Handle[i2c-4:
fd=52], Keeping adjusted sleep multiplier 2.00 for SE_POST_WRITE or
SE_POST_SAVE_SETTINGS
Nov 23 17:42:59 bazzite org_kde_powerdevil[2744]: dh=Display_Handle[i2c-3:
fd=52], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or
SE_POST_SAVE_SETTINGS
Nov 23 17:43:01 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
[DDCutilDisplay]: ddca_get_non_table_vcp_value -3007
Nov 23 17:43:01 bazzite org_kde_powerdevil[2744]: dh=Display_Handle[i2c-5:
fd=52], Keeping adjusted sleep multiplier 2.00 for SE_POST_WRITE or
SE_POST_SAVE_SETTINGS
Nov 23 17:43:03 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
[DDCutilDisplay]: ddca_get_non_table_vcp_value -3007
Nov 23 17:43:03 bazzite org_kde_powerdevil[2744]: dh=Display_Handle[i2c-4:
fd=52], Keeping adjusted sleep multiplier 2.00 for SE_POST_WRITE or
SE_POST_SAVE_SETTINGS
Nov 23 17:44:25 bazzite org_kde_powerdevil[2744]: dh=Display_Handle[i2c-3:
fd=52], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or
SE_POST_SAVE_SETTINGS
Nov 23 17:44:27 bazzite org_kde_powerdevil[2744]: org.kde.powerdevil:
[DDCutilDisplay]: ddca_get_non_table_vcp_value -300

[kwin] [Bug 497113] New: Kwin wayland crashed randomly while fullscreen video was playing

[test user]

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

Bug ID: 497113
   Summary: Kwin wayland crashed randomly while fullscreen video
was playing
Classification: Plasma
   Product: kwin
   Version: 6.1.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: excellentadvers...@distruzione.org
  Target Milestone: ---

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

SUMMARY

Hi
I was watching a video on full screen and has few other windows like browsers,
kate and konsole were open. The screen went black suddenly and came back with
firefox crash reporter. The browser crashed because wayland connection was
lost. (KDE/QT apps survived because of compositor restarting support). I
checked coredumps and indeed kwin crashed but without any relevant logging in
journal. KCrash generated emty backtrace so I manually did it and attaching it
here. Upon basic debugging I find no apparent reason so far.

STEPS TO REPRODUCE
1. That's the difficult part. It was random and not reproducible afaik. Only
hint is the coredump.
I do not recall any previous compositor crash, at least after plasma 6.

OBSERVED RESULT
kwin_wayland crashed

EXPECTED RESULT
It doesn't crash

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.11.3-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION
Backtrace attached. I'll attach coredump later due to size limits.

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

[kwin] [Bug 497113] Kwin wayland crashed randomly while fullscreen video was playing

[test user]

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

--- Comment #1 from test user  ---
The compressed coredump:

core.kwin_wayland.1000.b41b6fbacaaa4f6aa9531a32dd934035.1773.173342067700.zst
https://0x0.st/X7I8.zst

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

[kwin] [Bug 497113] Kwin wayland crashed randomly while fullscreen video was playing

[test user]

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

test user  changed:

   What|Removed |Added

 CC||excellentadversary@distruzi
   ||one.org

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

[plasmashell] [Bug 494262] On Wayland, desktop on one monitor of a multi-monitor setup is black/missing after unlocking

[KDE User]

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

--- Comment #15 from KDE User  ---
Sorry for double posting. I forgot to include my latest system information.

Operating System: Bazzite 41
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.12-203.bazzite.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H WIFI

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

[plasmashell] [Bug 494262] On Wayland, desktop on one monitor of a multi-monitor setup is black/missing after unlocking

[KDE User]

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

--- Comment #14 from KDE User  ---
Just updating my experience with this bug. It seems to have magically vanished
over the course of several updates. I did change my panel arrangements and I am
using a live wallpaper with the help of Wallpaper Engine for KDE so it could be
that too. I used to have 2 panels - one long one on the top and a small
docklike panel on the bottom. Now I have the one long panel on the bottom
similar to the Windows 11 layout and I no longer experience this issue.

I know this probably doesn't help with identifying the root cause of the bug
but if other people experiencing the same issue could maybe try changing their
layout to be like mine and seeing if the issue still exists could confirm if
it's a specific arrangement that leads to this bug.

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

[systemsettings] [Bug 503686] New: Feedback and Bug Report: UX Issues and Inconsistencies in KDE's Color Scheme Editor

[KDE User]

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

Bug ID: 503686
   Summary: Feedback and Bug Report: UX Issues and Inconsistencies
in KDE's Color Scheme Editor
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: cecij72...@firain.com
  Target Milestone: ---

SUMMARY

Hi KDE team,

First of all, thank you for the incredible work you continue to do. KDE is one
of the most powerful and flexible desktop environments out there, and features
like the Edit Color Scheme tool really highlight that. I wanted to share some
thoughts and observations from my recent experience using this feature—mainly
around a few quirks and potential improvements that could help polish the user
experience even further. This bug report addresses several UX issues and bugs
in KDE’s foreground color editor, found under Settings > Colors > Edit Color
Scheme (the dialog that opens after clicking the pencil icon on each color
theme).

One issue I noticed is that when I use the "Save As" option to create a new
color scheme, the changes don’t immediately reflect in the UI. I often need to
switch pages or navigate away and back again before the new theme appears
correctly. Similarly, after making changes through the Edit Color Scheme dialog
and saving them, the Apply button remains disabled—even though a modification
was clearly made. From a UX perspective, enabling that button post-save would
offer a clear signal to the user that changes are ready to be applied.

There’s also some confusion when trying to apply the saved theme. After saving
edits, the theme doesn’t immediately take effect until I switch to another
theme and then back again. It creates a feeling that the system didn’t register
the changes, which might be discouraging for users trying to explore
customization.

Another point I’d love to highlight: the Edit Color Scheme button itself could
be emphasized a bit more in the UI. It’s a powerful customization feature, yet
it's easy to overlook—especially for users who assume they can only change
accent colors. Foreground color editing is a big deal, and many users (myself
included) didn’t even realize it was possible for the longest time.

This becomes even more important with KDE 6.4, which introduces a darker
foreground by default. While many users may welcome the new aesthetic, others
might prefer something lighter or different for accessibility or personal
taste. Giving more visibility to the color editing options will help people
discover and appreciate just how customizable KDE really is.

A few more observations:

- When I copy and darken the Breeze theme, everything seems fine—until I focus
on other application windows, at which point the theme partially reverts to
default Breeze colors for unfocused windows. I confirmed that all relevant
values were updated, so this may be a rendering or caching issue.
Interestingly, when I start with a stock dark theme and customize it, this
issue doesn’t occur. That suggests the bug might be linked specifically to
saving or modifying derived themes based on Breeze. Or this also suggests that
color editing options might be missing.

- Additionally, updating the tab buttons to use the modern, evenly distributed
style that fills the available space would improve consistency with other parts
of the system where this standard layout is already being used.

- Finally, I've noticed that some color changes don’t save correctly. It's
possible this is related to built-in contrast enforcement, which is
understandable. But given how much freedom KDE already provides with accent
colors, it might make sense to offer users full control here—even if it means
letting them choose combinations with poor contrast. Sometimes, creative
expression trumps readability.

Overall, despite the hiccups, I’ve really enjoyed using this feature. It adds a
lot of personality to the desktop, and I deeply appreciate that KDE gives users
this level of control. These suggestions come from a place of admiration for
the work already done—and excitement for what’s ahead. KDE 6.4 is a great
update, and it would be even better if the bugs in the foreground color editor
were fixed!

Apologies for using AI to help write this—I relied on it because my grammar
isn’t the best, and the message would have been much less clear if I had
written it entirely on my own.

Thanks again for all your hard work and dedication to making KDE amazing!

Warm regards,
A grateful KDE user and tinkerer

STEPS TO REPRODUCE
1. (Many, listed above)
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

[systemsettings] [Bug 503686] Feedback and Bug Report: UX Issues and Inconsistencies in KDE's Color Scheme Editor

[KDE User]

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

KDE User  changed:

   What|Removed |Added

Version|unspecified |6.3.4
   Keywords||accessibility, usability

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

[systemsettings] [Bug 503686] Feedback and Bug Report: UX Issues and Inconsistencies in KDE's Color Scheme Editor

[KDE User]

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

KDE User  changed:

   What|Removed |Added

  Alias||KColorSchemeEditor

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

[systemsettings] [Bug 504007] New: Clicking "Save As" on KColorSchemeEditor does not update the list of available color schemes

[KDE User]

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

Bug ID: 504007
   Summary: Clicking "Save As" on KColorSchemeEditor does not
update the list of available color schemes
Classification: Applications
   Product: systemsettings
   Version: git-stable-Plasma/6.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_colors
  Assignee: plasma-b...@kde.org
  Reporter: cecij72...@firain.com
CC: noaha...@gmail.com, tantalising...@gmail.com,
uhh...@gmail.com
  Target Milestone: ---

SUMMARY
Clicking "Save As" on KColorSchemeEditor does not update the list of available
color schemes, closing and reopening the application updates the list.

STEPS TO REPRODUCE
1. Go to System settings -> Colors & Themes -> Colors -> Edit Color Scheme
(edit any desired color scheme)
2. Click "Save As" and give it a name and press "Ok"
3. The list color schemes list won't update

OBSERVED RESULT
The color schemes list didn't update, leading to me believing the feature
doesn't work

EXPECTED RESULT
The list immediately gets updated after clicking "Ok"

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

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 504009] New: Clicking "Save" after updating a color scheme doesn't change Plasma's color

[KDE User]

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

Bug ID: 504009
   Summary: Clicking "Save" after updating a color scheme doesn't
change Plasma's color
Classification: Applications
   Product: systemsettings
   Version: git-stable-Plasma/6.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_colors
  Assignee: plasma-b...@kde.org
  Reporter: cecij72...@firain.com
CC: noaha...@gmail.com, tantalising...@gmail.com,
uhh...@gmail.com
  Target Milestone: ---

SUMMARY
Clicking "Save" after updating a color scheme doesn't change Plasma's color,
the user has to select and apply another color scheme and then re-select the
changed color scheme

STEPS TO REPRODUCE
1. Go to System settings -> Colors & Themes -> Colors -> Edit Color Scheme
(edit any desired custom color scheme)
2. Change one or more than one color in there and click on "Save"
3. Plasma's color won't update, the user needs to select and apply another
color scheme and then re-select the updated color scheme to change Plasma's
color

OBSERVED RESULT
Plasma's color didn't update

EXPECTED RESULT
Plasma's color immediately gets updated after clicking "Save"

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

ADDITIONAL INFORMATION

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

[kommit] [Bug 469392] Dark icons on dark colorscheme

[KDE User]

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

KDE User  changed:

   What|Removed |Added

 CC||cecij72...@firain.com

--- Comment #2 from KDE User  ---
(In reply to Hamed Masafi from comment #1)
> Thanks for reporting
> This added to my list and will be fixed soon

Hello there. The Flatpak version of Kommit still has this issue.

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

[plasmashell] [Bug 504189] New: kscreenlocker allows clipboard paste in lock screen

[test user]

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

Bug ID: 504189
   Summary: kscreenlocker allows clipboard paste in lock screen
Classification: Plasma
   Product: plasmashell
   Version: 6.3.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Screen locking
  Assignee: plasma-b...@kde.org
  Reporter: excellentadvers...@distruzione.org
  Target Milestone: 1.0

SUMMARY

kscreenlocker password prompt enables anyone to paste clipboard or primary
selection content in it. Clipboards can potentially include sensitive data
(even passwords if copied from password manager) and should not be accessible
to anyone from a locked computer.

STEPS TO REPRODUCE
1. copy some text
2. lock screen
3. press paste shortcut (ctrl +v usually) inside password box

OBSERVED RESULT

copied text pasted

EXPECTED RESULT

no text pasted

SOFTWARE/OS VERSIONS
all

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

[plasmashell] [Bug 504189] kscreenlocker allows clipboard paste in lock screen

[test user]

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

test user  changed:

   What|Removed |Added

 CC||excellentadversary@distruzi
   ||one.org

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

[plasmashell] [Bug 504189] kscreenlocker allows clipboard paste in lock screen

[test user]

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

test user  changed:

   What|Removed |Added

Version|6.3.4   |master

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

[plasmashell] [Bug 504484] New: Have more control over date and time's individual font sizes and alignment

[KDE User]

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

Bug ID: 504484
   Summary: Have more control over date and time's individual font
sizes and alignment
Classification: Plasma
   Product: plasmashell
  Version First git-stable-Plasma/6.3
   Reported In:
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Digital Clock widget
  Assignee: plasma-b...@kde.org
  Reporter: cecij72...@firain.com
  Target Milestone: 1.0

A feature to have more fine-grained control over how Digital Clock widget's
time and date is shown on the taskbar would be a great addition. For example,
on Windows, the time is above and the date is below. But they are not center
aligned like in KDE, they are aligned to the right while having the same sized
fonts for them both. There are people who would prefer a different alignment
over one.

Another issue is, the time is bigger than the date. A more fine-grained
approach like having the ability to edit individual font sizes of both date and
time, and being able to align them on to the left, right or middle would be a
very nice feature.

A user checks the time a lot throughout the day. Being able to customize the
individual font sizes and being able to align left, right, and center would be
an amazing feature that would make the widget more feature complete. It would
also improve accessibility, as people would be able to tune how the date and
time is shown to their liking.

It's one of the things that looked odd to me when I first switched to KDE from
Windows. The date and time looked different, and when I wanted to make it look
like Windows, I couldn't! This feature would allow people who prefer or are
more used to different way of looking at date and time edit for their own
needs. Not to mention that it would also benefit aesthetics too! Thanks!

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

[plasmashell] [Bug 504484] Have more control over date and time's individual font sizes and alignment

[KDE User]

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

KDE User  changed:

   What|Removed |Added

   Keywords||accessibility

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

[plasmashell] [Bug 504249] global menu dropdown subitems list glitched first time

[test user]

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

--- Comment #3 from test user  ---
I doubt that. I've not seen it with menus in any other app nor with 
plasma popup menus.

On 5/19/25 00:29, Nikita Tsukanov wrote:
> https://bugs.kde.org/show_bug.cgi?id=504249
>
> --- Comment #2 from Nikita Tsukanov  ---
> This doesn't seem to happen with X11, so I believe it's a KWin bug
>

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

[plasmashell] [Bug 504249] New: global menu dropdown subitems list glitched first time

[test user]

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

Bug ID: 504249
   Summary: global menu dropdown subitems list glitched first time
Classification: Plasma
   Product: plasmashell
   Version: 6.3.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Global Menu widget
  Assignee: plasma-b...@kde.org
  Reporter: excellentadvers...@distruzione.org
CC: k...@privat.broulik.de, mvourla...@gmail.com
  Target Milestone: 1.0

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

SUMMARY

Submenu items of plasma global menu are displayed corrupted or in wrong scale.
I have seen this does not occur for a specific item with submenu after the
submenu list is displayed once.

STEPS TO REPRODUCE
1. Have globalmenu widget enabled. open any application with app menu (most kde
app).
2. Hover over a menu dropdown item  and reveal the submenu list.
3. Hover over same item again after closing the menu.

OBSERVED RESULT

Submenu list renders with magnified fonts, sometimes corrupted.

EXPECTED RESULT

List should render normal.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Graphics Platform: Wayland
Graphics Processor 1: Intel® UHD Graphics

ADDITIONAL INFORMATION
see the screenshot for explanation.

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

[KScreen] [Bug 506661] New: HDMI display replication fails on KDE Plasma 6.4.0 - no signal sent to TV when set as replica of main display

[KDE User]

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

Bug ID: 506661
   Summary: HDMI display replication fails on KDE Plasma 6.4.0 -
no signal sent to TV when set as replica of main
display
Classification: Plasma
   Product: KScreen
  Version First 6.4.0
   Reported In:
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: kde.h2...@simplelogin.com
  Target Milestone: ---

SUMMARY

Attempting to replicate my main display on my TV over HDMI is causing no signal
to be sent to the TV. However, setting the TV to be it's own screen (Replica of
None) works correctly.

STEPS TO REPRODUCE
1. Connect TV via HDMI
2. Set TV screen to be a replica of the main display
3. Apply

OBSERVED RESULT

No signal sent to the TV

EXPECTED RESULT

TV receiving a signal and the main display replicated to the TV.

SOFTWARE/OS VERSIONS

Operating System: Bazzite 42
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.14.6-109.bazzite.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060 Ti
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H WIFI

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

[okular] [Bug 480191] Allow user to disable JavaScript support.

[KDE User]

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

KDE User  changed:

   What|Removed |Added

 CC||cecij72...@firain.com

--- Comment #1 from KDE User  ---
+1 for a checkbox to disable JS in the settings. Other document readers like
Evince and GNOME Papers don't support JavaScript for PDFs for security reasons.
Most malicious PDF documents contain JavaScript. As corporate environments have
to check PDF attachments a lot, an option to disable JavaScript would improve
security and reliability in a corporate environment, as well as for any user
who prefers to disable JavaScript.

It could also improve performance for some PDFs, not to mention the positive
effect it could have on the environment for not running JS and wasting CPU
cycles for a PDF, which could very likely be a malicious file. Most people use
PDFs to view formatted texts and images (media), and are unaware of scripts
running behind the scene. So, an option to disable JS in PDFs is a very useful,
and in my opinion, a must have feature.

I would be very grateful if such a feature exists, as a user who deals with
hundreds of PDFs. Thank you, hope to catch the Okular contributors' attention
with this.

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

[yakuake] [Bug 503706] Yakuake doesn't open in the correct position for the first time on that monitor

[Zmail User]

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

Zmail User  changed:

   What|Removed |Added

 CC||bugs.kde.org@zmail.contact

--- Comment #5 from Zmail User  ---
>KDE Plasma Version: 6.4.3
>KDE Frameworks Version: 6.16.0
>Qt Version: 6.9.1
>Kernel Version: 6.16.0-2-cachyos
>Graphics Platform: Wayland

** Summary:**
Yakuake dropdown terminal uses wrong monitor dimensions on first toggle after
moving mouse between monitors with different resolutions. Uses cached
dimensions from previous monitor until toggled off/on again.

**Environment:**
- Dual monitors with different resolutions
- Yakuake set to "Open at mouse position"

**Steps to Reproduce:**
1. Move mouse to Monitor 1 (e.g. 1920x1080)
2. Toggle Yakuake (F12) - displays correctly
3. Close Yakuake
4. Move mouse to Monitor 2 (e.g. 3440x1440) 
5. Toggle Yakuake - ***first time shows wrong size*** (uses Monitor 1
dimensions on Monitor 2)
6. Toggle off and on again - now shows correct size

**Expected Result:**
Yakuake should immediately use correct dimensions for current monitor

**Actual Result:**
First toggle after mouse movement uses previous monitor's cached dimensions.
Second toggle works correctly.

**Workaround:**
Double-toggle Yakuake after moving mouse between monitors

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

[digikam] [Bug 411099] Search: Avoid search without user input (void fields)

[Rafael Linux User]

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

--- Comment #19 from Rafael Linux User  ---
Peter, unfortunately, I understand that if nothing has been done about it in
the searches since 2019 to date, then they don't see it as an issue. Most
likely because they don't work with hundreds of thousands of photos on a daily
basis. 

Moreover, to date, I know users who, in order to avoid this problem, prefer to
use the o.s. file manager search and thus avoid the waiting time that occurs
because of what I have already mentioned in my previous messages.

Regards

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

[digikam] [Bug 411099] Search: Avoid search without user input (void fields)

[Rafael Linux User]

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

--- Comment #21 from Rafael Linux User  ---
(In reply to Syv from comment #20)
> On Sat, 26 Feb 2022 22:53:15 +
> "Rafael Linux User"  wrote:
> 
> > https://bugs.kde.org/show_bug.cgi?id=411099
> > 
> > --- Comment #19 from Rafael Linux User
> > Most likely because they don't work with hundreds of thousands of
> > photos on a daily basis.
> 
> I don't have hundredS of thousands but I deal in tenS of thousands. I
> also am not enthusiastic about the "re-search'
> 
> My solution is much more low-tech and is user dependent. 
> 
> When I'm done with my search, I press the reset button.

Indeed, as you do not have hundreds of thousands, you are unaware that while
the automatic search is being performed by clicking on "Search", the interface
is often blocked and allows you to click on "Reset". Fortunately for you, you
will not have this problem.

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

[plasmashell] [Bug 454790] New: Plasma doesn't let drop items to second monitor applications when using 4K monitor as source

[Rafael Linux User]

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

Bug ID: 454790
   Summary: Plasma doesn't let drop items to second monitor
applications when using 4K monitor as source
   Product: plasmashell
   Version: 5.24.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: rafael.linux.u...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
Scenario: OpenSUSE Tumbleweed, with 2 monitors (4K monitor and 1024 pixels
width monitor).
Since I installed my 4K monitor (primary monitor) that replaced my FHD previous
monitor (primary monitor too) Plasma let me drag from primary monitor to
secondary monitor but don't drop the objects dragged.  For example, I can have
one Dolphin window opened in each monitor. If I try to drag and drop a file
from Dolphin showed in primary monitor to Dolphin in secondary monitor, the
file is not dropped!!! (mouse pointer changes to "prohibited" icon). I
discovered this issue when, as I usually do, I drag a mp3 file to my music
player on secondary monitor.

STEPS TO REPRODUCE
1. Drag a file from 4K monitor
2. Drop it to second monitor

OBSERVED RESULT
Plasma don't let to drop the file

EXPECTED RESULT
To drop the file as always

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220502
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.16.4-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: llvmpipe

ADDITIONAL INFORMATION
New monitor uses same Display Port cable on same graphic card GPU

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

[plasmashell] [Bug 454790] Plasma doesn't let drop items to second monitor applications when using 4K monitor as source

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael Linux User  ---
I can drop from secondary monitor to primary monitor (4K) but not vice versa.

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

[plasmashell] [Bug 449429] [NVIDIA] Panel and dialog rendering display graphical corruption under wayland

[Lucius Q. User]

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

Lucius Q. User  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Lucius Q. User  ---
Fixed in 5.25

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

[plasmashell] [Bug 351175] Panel on screen edge between two monitors does not auto hide

[Rafael Linux User]

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

--- Comment #48 from Rafael Linux User  ---
(In reply to Corban from comment #47)
> Just updated to plasma 5.27 and this is still a problem despite the
> "Multi-monitor overhaul"

That the problem is not solved was not a surprise to me, because they don't
consider it a priority. Anyway, I installed it and tested if the problem was
solved "unexpectedly" (just as unexpectedly, it appeared).

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

[digikam] [Bug 466132] New: Can't launch Digikam after upgrade KDE Plasma to 5.27 (error while loading libopenblas.so.0)

[Rafael Linux User]

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

Bug ID: 466132
   Summary: Can't launch Digikam after upgrade KDE Plasma to 5.27
(error while loading libopenblas.so.0)
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

SUMMARY
Something is happening before upgrading to KDE Plasma 5.2.7. In the two PC's I
upgraded, Digikam doesn't launch. It gives in terminal an error:
digikam: error while loading shared libraries: libopenblas.so.0: cannot open
shared object file: No such file or directory

STEPS TO REPRODUCE
1. Upgrade or install KDE Plasma to 5.2.7
2. Launch Digikam

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
To open Digikam

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230214
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.10-1-default (64-bit)
Graphics Platform: X11
Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2

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

[digikam] [Bug 466134] New: Better task progress information

[Rafael Linux User]

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

Bug ID: 466134
   Summary: Better task progress information
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: unspecified
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

SUMMARY
I have been using digikam for many years and there is something I have always
hoped for improvement, but as the improvement is not coming and maybe nobody
has suggested it, I am doing it here now.

Currently, when processes are performed, the "Digikam" logo transforms into an
animated icon. This is not very useful, because it does not show the estimated
time or at least a percentage bar of the process in progress. Moreover, in
certain screen configurations, for example, a vertical screen or a low
horizontal resolution, this animation is NOT visible, because it is hidden (the
user has to click to enlarge the toolbar and see the animation).

What would be really useful is to show a progress bar of the activity in
progress in the status bar, even if the estimated time to finish it is not
shown. 

I really miss such information when I import images, which are usually in RAW
format, and the import becomes tedious because the progress bar is not
displayed.

Thank you

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

[digikam] [Bug 466134] Improve task progress information

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

Summary|Better task progress|Improve task progress
   |information |information
 CC||rafael.linux.u...@gmail.com

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

[digikam] [Bug 466134] Improve task progress information

[Rafael Linux User]

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

--- Comment #4 from Rafael Linux User  ---
(In reply to Maik Qualmann from comment #2)
> I think it's about the import tool.
> 
> When loading the content, we don't know the number of items coming,
> especially with the GPhoto2 driver, so just an animated logo to see
> something is working. There is a progress bar when downloading items.
> 
> Maik

Yes, the import tool. When importing I select previously files to move and
delete (very useful combination), select or create destiny folder and begin the
procedure (you are right, not "process") and I don't see a percentage bar or a
"N of  M files copied/moved" (maybe I'm looking the wrong place).

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

[digikam] [Bug 466134] Improve task progress information

[Rafael Linux User]

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

--- Comment #6 from Rafael Linux User  ---
You all have reason. I was looking for a bigger or visible bar, like device
capacity or album capacity ones. They are clearly visible. Honestly, until you
told me where it appeared, this progress line went unnoticed by me, who already
have some visual problems. That's why I suggest changing the format to a bar
similar to the ones mentioned above that show the percentage available on the
memory card, i.e. with a fixed width and a height equal to the other
percentages, showing progressively the percentage achieved.

Thank you

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

[digikam] [Bug 465680] Fails to start due to missing library in openSUSE

[Rafael Linux User]

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

--- Comment #14 from Rafael Linux User  ---
(In reply to Maik Qualmann from comment #11)
> The problem seems to have been found:
> 
> https://bugzilla.suse.com/show_bug.cgi?id=1208248
> 
> Maik

Thank you. I did a rollback to Plasma 5.26 while openSUSE fix issue.

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

[digikam] [Bug 465680] Fails to start due to missing library in openSUSE

[Rafael Linux User]

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

--- Comment #16 from Rafael Linux User  ---
(In reply to Maik Qualmann from comment #15)
> With today's openSUSE Tumbleweed update the problem with libopenblas is
> fixed.
> 
> Maik

Thank you!!! I just upgraded again to 5.27 and Digikam again works!!!

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

[digikam] [Bug 466873] New: Batch conversion to WEBP and AV1 format

[Rafael Linux User]

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

Bug ID: 466873
   Summary: Batch conversion to WEBP and AV1 format
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: BatchQueueManager-Plugins
  Assignee: digikam-bugs-n...@kde.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

I was surprised when, despite Digikam can export to avif and webp, however I
didn't find those formats to export in batch mode. 

Please, could you add to batch process in some future Digikam version?

Thank you

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

[digikam] [Bug 466876] New: LightTable: Selected image properties are not showed when clicking each image

[Rafael Linux User]

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

Bug ID: 466876
   Summary: LightTable: Selected image properties are not showed
when clicking each image
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: LightTable-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

SUMMARY
Usually, I use LightTable to compare even distinct formats of same image. I
choose an image and click on "Properties" panel on right pane to show its
properties. However, properties showed are always same, not from the
corresponding selected image.

STEPS TO REPRODUCE
1. Choose two distinct format images
2. Click on "LightTable"
3. Open right side "Properties" panel. Selected image properties are showed
4. Select the second image. Properties showed are the same than before, not the
selected one properties.

OBSERVED RESULT
Properties showed are always same, not the selected image properties.

EXPECTED RESULT
To show selected image properties

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230221
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.12-1-default (64-bit)
Graphics Platform: X11

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

[digikam] [Bug 466873] Batch conversion to WEBP and AV1 format

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael Linux User  ---
(In reply to Maik Qualmann from comment #1)
> Conversion to webp and avif has already been added to digiKam-8.0.0.
> 
> Maik

Great!!! Thank you, and sorry about asking something we will have soon!!!

;)

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

[digikam] [Bug 466876] LightTable: Selected image properties are not showed when clicking each image

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #4 from Rafael Linux User  ---
Thank you to all.

The truth is that it didn't even occur to me that in LightTable mode left panel
changed to a clone of right panel.

In my opinion, of course, it is not very intuitive. Also, it makes it more
difficult to look at the changes, as you have to look from one end of the
screen to the other, when it would be quicker and easier to keep a single pane,
as in the main Digikam window. It is precisely for this reason that the user
tends to visualise the information in the same way as in the main window.

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

[Spectacle] [Bug 467001] New: Enhancing "Numeric pointer" tool

[Rafael Linux User]

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

Bug ID: 467001
   Summary: Enhancing "Numeric pointer" tool
Classification: Applications
   Product: Spectacle
   Version: 22.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: rafael.linux.u...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
When using "numeric pointer" tool, numbering is automatically increased.
However, if user undo last "numeric pointer" object insertion step, numeration
not "decreased", so user must change it manually.

I think this behaviour could be enhanced as if user do a "undo" and last used
action was to add a "numeric pointer", Spectacle should decrease numeration
too.

;)

Thank you

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

[Spectacle] [Bug 467001] Enhancing "Numeric pointer" tool

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael Linux User  ---
(In reply to Nate Graham from comment #1)
> This is an issue in the 3rd-party KImageAnnotator library that we use here;
> please report it at https://github.com/ksnip/kImageAnnotator/issues. Thanks!

Ok, thanks

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

[Discover] [Bug 458732] Discover should retry downloading the package when some issues (curl) happens

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael Linux User  ---
(In reply to Nate Graham from comment #1)
> Discover uses the PackageKit library for this; it's up to either PackageKit
> or the underlying package management backend to be more resilient to this
> type of condition.
> 
> Ideally the actual package servers would be more reliable too.

I agree partially. I understand Discover want a "clean" working mode, without a
bunch of messages for user when errors happen but why not at least to show a
message to user about what choices he has available? I don't know how to
proceed. I asked here cause I like Discover simplicity and user friendly
information about each application. But this issue is a headache for me, an
average linux user, so you can imagine a beginner user we'll desperate with
this kind of issues.

Thank you
Yast instaler (Zypp-main and sw_single_wrapp)

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

[Discover] [Bug 458732] Discover should retry downloading the package when some issues (curl) happens

[Rafael Linux User]

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

--- Comment #5 from Rafael Linux User  ---
(In reply to Aleix Pol from comment #4)
> Can you check with pkcon which error message you get?

When I need to launch pkcon? Before launch Discover or when a error appears?
I'll have not a quick reply to that, cause usually issue happens when I have a
lot of packages to update (more than 100) but please, tell how to use and I'll
try to do this week in my PCs.

Thank you!!

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

[Discover] [Bug 458732] Discover should retry downloading the package when some issues (curl) happens

[Rafael Linux User]

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

--- Comment #6 from Rafael Linux User  ---
I'm sorry. How to use pkcon? It needs parameters and don't know which they are.
Could you help me about it?

Thank you

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

[Discover] [Bug 458732] Discover should retry downloading the package when some issues (curl) happens

[Rafael Linux User]

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

--- Comment #8 from Rafael Linux User  ---
It seems pkcon doesn't work as expected. I'll explain:
"pkcon update" output is:

(0%)  Falló la orden: Repository unknown  (command failed is translation)

In fact, I did "pkcon --help" and that parameter doesn't appear. Anyway,
"googling" I found:
1 - pkcon refresh  (worked)
2 - pkcon update (began to do something), till it output this error:

Error grave: problema con el elemento libpoppler123-22.08.0-324.4.x86_64
instalado
problema con el elemento libpoppler123-32bit-22.08.0-324.4.x86_64 instalado

(prblema con el elemento = trouble with element installed)

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

[Discover] [Bug 458732] Discover should retry downloading the package when some issues (curl) happens

[Rafael Linux User]

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

--- Comment #10 from Rafael Linux User  ---
(In reply to Nate Graham from comment #9)
> Sounds like there's a problem with the repo configuration on your machine.

I forgot to comment: Just after I did that commands, I did "sudo zypper dup",
and works like always and, as usually, it ask me to take actions:

2 problemas: (issues)
Problema: problema con el elemento libpoppler123-22.08.0-324.4.x86_64 instalado
Problema: problema con el elemento libpoppler123-32bit-22.08.0-324.4.x86_64
instalado

Problema: problema con el elemento libpoppler123-22.08.0-324.4.x86_64 instalado
 Solución 1: instalar libpoppler123-22.08.0-1.2.x86_64 del proveedor openSUSE
 reemplazando libpoppler123-22.08.0-324.4.x86_64 del proveedor
obs://build.opensuse.org/LibreOffice
 Solución 2: mantener el elemento libpoppler123-22.08.0-324.4.x86_64 obsoleto

Elija las soluciones usando '1' u omitir, reintentar o cancelar [1/2/o/r/c/i/?]
(c): 1

Problema: problema con el elemento libpoppler123-32bit-22.08.0-324.4.x86_64
instalado
 Solución 1: instalar libpoppler123-32bit-22.08.0-1.2.x86_64 del proveedor
openSUSE
 reemplazando libpoppler123-32bit-22.08.0-324.4.x86_64 del proveedor
obs://build.opensuse.org/LibreOffice
 Solución 2: mantener el elemento libpoppler123-32bit-22.08.0-324.4.x86_64
obsoleto

Elija las soluciones usando '1' u omitir, reintentar o cancelar [1/2/o/r/c/i/?]
(c): 1
Resolviendo dependencias...
Calculando actualización de distribución...

And that's the fact. "Zypper" or "Yast" give options to user and finally can
update/upgrade/install, but discover does not, so finally user need to use
"ugly" ways to get it and can't use Discover  :(

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

[Discover] [Bug 458732] Discover should retry downloading the package when some issues (curl) happens

[Rafael Linux User]

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

--- Comment #20 from Rafael Linux User  ---
(In reply to Nate Graham from comment #16)
> At least back when I was using OpenSUSE Tumbleweed, it was very common to
> have the 3rd-party PacMan repo enabled, as that was the only way to get
> medic codecs for tons of patented video and audio file formats. And having
> that repo led to this situation all the time for me.
> 
> I'm now using Fedora with the RPMFusion repo installed for the same purpose,
> and it never needs user interaction to resolve potentially ambiguous
> packaging situations. It manages to resolve them itself without asking me.

It's true, but neccesary. NVidia, Mozilla, Chrome, LibreOffice,
VisualStudioCode  are another example of external repositories that users
need to add and, some times, they can fail.

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

[Discover] [Bug 458732] Discover should retry downloading the package when some issues (curl) happens

[Rafael Linux User]

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

--- Comment #21 from Rafael Linux User  ---
I must add something that still now, in 2022, I can't understand why openSUSE
do this way. If user add a repository and the sign key for it, when user click
on "check update" from icon in taskbar,  if user didn't accepted key for that
repository, openSUSE shows "Signature verification for Repository -name of
repository-  failed " and then user must go to console , do a "zypper refresh"
, accept  sign key (typing "yes") and then user can continue from desktop. That
should not happen neither. Update desktop icon should ask about accept sign key
to do things easier for user.

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

[krename] [Bug 411067] Add command line argument (and action) for folder-only rename

[Rafael Linux User]

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

--- Comment #10 from Rafael Linux User  ---
Not underrated by you, but by KDE   ;)

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

[kwin] [Bug 432053] Nvidia Wayland - High CPU Usage

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #4 from Rafael Linux User  ---
Similar issue, but making Plasma unusable (100% CPU  1 core usage). In my case,
all is so slow that moving mouse takes 3 to 4 seconds each time. "kwin_wayland"
is the process eating CPU. These are the sub-threads involved (from perf.data):
- kms_swrast_dri.so (repeated x 5 times) at 99.3% CPU
- libc.so.6 (repeated x 2 times) at  99.3% CPU

Operating System: openSUSE Tumbleweed 20230527
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2

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

[kwin] [Bug 470427] New: "kwin_wayland" overloading CPU getting unusable desktop

[Rafael Linux User]

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

Bug ID: 470427
   Summary: "kwin_wayland" overloading CPU getting unusable
desktop
Classification: Plasma
   Product: kwin
   Version: 5.27.5
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

Created attachment 159328
  --> https://bugs.kde.org/attachment.cgi?id=159328&action=edit
perf.data view

SUMMARY
Enabling Wayland session in Plasma I got an unusable desktop. 1 CPU  core is
used at 100%). All is so slow that moving mouse takes 3 to 4 seconds each time,
jumping from one place to next, like if FPS dropped all over desktop. 

"kwin_wayland" is the process eating CPU. These are the sub-threads involved (I
got from perf.data):
- kms_swrast_dri.so (repeated x 5 times) at 99.3% CPU
- libc.so.6 (repeated x 2 times) at  99.3% CPU

STEPS TO REPRODUCE
1. Select Wayland before authenticate user
2. Authenticate user
3. Desktop works like 1/10 of normal speed

OBSERVED RESULT
If I switch to Ctrl+Alt+F1 and come back to desktop, I only have mouse pointer
over a black desktop. No way to click nothing, cause there is nothing to click
in, only a black background and my mouse pointer.

EXPECTED RESULT
To work like with X Org Session

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230527
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2

ADDITIONAL INFORMATION
Nvidia original repository drivers installed. No issues at all in X Window
session.

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

[kdeplasma-addons] [Bug 470445] New: [Wayland] Side panels "freeze", showing a NON-interactive snapshot of it.

[Rafael Linux User]

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

Bug ID: 470445
   Summary: [Wayland] Side panels "freeze", showing a
NON-interactive snapshot of it.
Classification: Plasma
   Product: kdeplasma-addons
   Version: git-stable-Plasma/5.27
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Switchers
  Assignee: plasma-b...@kde.org
  Reporter: rafael.linux.u...@gmail.com
CC: isma...@gmail.com
  Target Milestone: ---

Created attachment 159345
  --> https://bugs.kde.org/attachment.cgi?id=159345&action=edit
Output after reinit Plasma

SUMMARY
After some random time, panels containing graphical add-ons such as the
"Icon-only Task Manager" freezes, so they show a snapshot of their last state,
but hovering over them does nothing. Even when "entering edit mode" they are
not accessible. You can only restart Plasma to make them functional again. 


STEPS TO REPRODUCE
1. Add "Small icons" task switcher to some side panel
2. Work as usually

OBSERVED RESULT
After some time (I think that interacting, not without user interaction) side
panels containing "Icon-only Task Manager" doesn't respond. Any graphic addon
is non-responsive at all and even is not possible to edit them. Only "kquitapp5
plasmashell || killall plasmashell && kstart5 plasmashell" got them to work
again.



EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kdeplasma-addons] [Bug 470445] [Wayland] Side panels "freeze", showing a NON-interactive snapshot of it.

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #1 from Rafael Linux User  ---
I'm sorry, forgot system info:
Operating System: openSUSE Tumbleweed 20230422
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 6.2.12-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2

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

[plasmashell] [Bug 470445] [Wayland] Side panels "freeze", showing a NON-interactive snapshot of it.

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||niccolo.venera...@gmail.com
  Component|Task Manager and Icons-Only |Panel
   |Task Manager|

--- Comment #2 from Rafael Linux User  ---
More info: Panels are "frozen" regardless of the graphic add-ons that are
added. The problem is with the panel itself: It happens on panels with
"auto-hide" enabled.

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

[plasmashell] [Bug 470445] [Wayland] Side panels with "auto-hide" enabled "freeze", showing a NON-interactive snapshot of it.

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

Summary|[Wayland] Side panels   |[Wayland] Side panels with
   |"freeze", showing a |"auto-hide" enabled
   |NON-interactive snapshot of |"freeze", showing a
   |it. |NON-interactive snapshot of
   ||it.

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

[plasmashell] [Bug 470445] [Wayland] Side panels "freeze", showing a NON-interactive snapshot of it.

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

Summary|[Wayland] Side panels with  |[Wayland] Side panels
   |"auto-hide" enabled |"freeze", showing a
   |"freeze", showing a |NON-interactive snapshot of
   |NON-interactive snapshot of |it.
   |it. |

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

[plasmashell] [Bug 470445] [Wayland] Side panels "freeze", showing a NON-interactive snapshot of it.

[Rafael Linux User]

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

--- Comment #3 from Rafael Linux User  ---
(In reply to Rafael Linux User from comment #2)
> More info: Panels are "frozen" regardless of the graphic add-ons that are
> added. The problem is with the panel itself: It happens on panels with
> "auto-hide" enabled.

Not really. After continuing trying I can say "auto-hide" option doesn't does
not influence the reproduction of the problem. I have set up several panels
with the same widget but one with "auto-hide" enabled and one without it
enabled. Both freeze at different times but I can't identify the cause. From
that moment of "freezing" when hovering the mouse over the icons nothing
happens, nor are the icons updated according to the active windows.

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

[kwin] [Bug 470427] "kwin_wayland" overloading CPU getting unusable desktop

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael Linux User  ---
In fact, I compared two PCs with same S.O. but distinct Nvidia graphics cards.
In one Wayland works but not in the other. I compared info about "Windows
manager" and found two differences:
1 -  OpenGL platform interface is EGL in working Wayland PC, GLX in the other
one
2 - QT5 AND QT6 are installed in working Wayland PC, only QT5 is in the other
one

So, is it neccesary QT6 to get Wayland work??

Thank you for your comment

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

[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia

[Rafael Linux User]

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

--- Comment #17 from Rafael Linux User  ---
(In reply to Nate Graham from comment #16)
> *** Bug 470445 has been marked as a duplicate of this bug. ***

Is NOT a duplicate!!! My panels freezed are showed up  when I move mouse over
edges (I had them auto-hidding) but are not interactive (as I told in subject).
They don't react to mouse clicks or icons are highlighted. When mouse is over a
icon, it shows modal information and thumbnails, but it's the only reaction to
mouse over them.

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

[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia

[Rafael Linux User]

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

--- Comment #19 from Rafael Linux User  ---
Maybe I misunderstood, but this thread subject says "but not functionally" ....
so this user case, I understand that if he click on a "freezed" icon, it will
react and launch application   :/

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

[kmail2] [Bug 470691] New: "Phonebook" button doesn't bring any window

[Rafael Linux User]

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

Bug ID: 470691
   Summary: "Phonebook" button doesn't bring any window
Classification: Applications
   Product: kmail2
   Version: 5.23.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

SUMMARY
When I click on "Phonebook", nothing happens. "Phonebook" window doesn't
appear.

STEPS TO REPRODUCE
1. Click on "Phonebook"

OBSERVED RESULT
"Phonebook" window is not opened.

EXPECTED RESULT
To open "Phonebook" window

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230422
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 6.2.12-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 15.5 GiB of RAM

ADDITIONAL INFORMATION
I can open it thru "Tools, Phonebook"

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

[kmail2] [Bug 470692] New: Address book: Add multiple addresses at the same time

[Rafael Linux User]

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

Bug ID: 470692
   Summary: Address book: Add multiple addresses at the same time
Classification: Applications
   Product: kmail2
   Version: 5.23.1
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

SUMMARY
Please could you implement a simple way to add to the address book the items
that will make up the address book? I mean, right now you have to add ONE BY
ONE each of the people who are going to be part of the group, instead of
allowing you to select several addresses and add them all at once.

Both Thunderbird and other clients have had this possibility for many versions
and I was surprised that KMail does not have this possibility.

Thanks

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

[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia

[Rafael Linux User]

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

--- Comment #23 from Rafael Linux User  ---
(In reply to riemarukarurosu from comment #22)
> > There were a ton of bugfixes going into 5.27.5, so I just wonder if anyone
> > can replicate the issue on that version, and if perhaps a happy side effect
> > of one of those bugfixes was this issue being resolved?
> It's reported since 5.26 but some people recently update to 5.27 same bug, I
> can confirm that the bug persist

#MeToo

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