[kwin] [Bug 488835] New: When Going into the new "edit panel mode" drop downs are blocked

[Elite]

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

Bug ID: 488835
   Summary: When Going into the new "edit panel mode" drop downs
are blocked
Classification: Plasma
   Product: kwin
   Version: 6.1.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: ---

Created attachment 170708
  --> https://bugs.kde.org/attachment.cgi?id=170708&action=edit
Image showing the drop down behind the crontl box

When in the edit panel prompt, lest say its the top panel if you have something
far to the right the edit panel control box blocks the ability to remove the
widget. You can still right click to remove it. But i feel that's missing the
point of the nice redesign.

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

[kwin] [Bug 488836] New: When Going into the new "edit panel mode" drop downs are blocked

[Elite]

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

Bug ID: 488836
   Summary: When Going into the new "edit panel mode" drop downs
are blocked
Classification: Plasma
   Product: kwin
   Version: 6.1.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: ---

Created attachment 170709
  --> https://bugs.kde.org/attachment.cgi?id=170709&action=edit
Image showing the drop down behind the crontl box

When in the edit panel prompt, lest say its the top panel if you have something
far to the right the edit panel control box blocks the ability to remove the
widget. You can still right click to remove it. But i feel that's missing the
point of the nice redesign. 

Operating System: Garuda Linux 
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.5-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE

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

[kwin] [Bug 488836] When Going into the new "edit panel mode" drop downs are blocked

[Elite]

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

Elite  changed:

   What|Removed |Added

   Keywords||regression

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

[frameworks-kirigami] [Bug 488326] After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message

[Elite]

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

Elite  changed:

   What|Removed |Added

 CC||eliteamdgam...@gmail.com

--- Comment #12 from Elite  ---
Same issue here on garuda arch kde. 

I tried removing catch an reinstalling  knewstuff, kirigami, qt6-declarative. I
have not had a crash so i cant add a report but 

```qrc:/kcm/kcm_firewall/main.qml:152 Type Kirigami.InlineMessage unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type
KT.InlineMessage unavailable
qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign
object of type "TP.IconPropertiesGroup" to property of type
"IconPropertiesGroup_QMLTYPE_82*" as the former is neither the same as the
latter nor a sub-class of it.``` 

I will also provide a screen shot incase that helps anyone. 


Operating System: Garuda Linux 
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.6-1-cachyos (64-bit)
Graphics Platform: Wayland

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

[frameworks-kirigami] [Bug 488326] After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message

[Elite]

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

--- Comment #13 from Elite  ---
Created attachment 170796
  --> https://bugs.kde.org/attachment.cgi?id=170796&action=edit
What the bug looks like when you click a affected setting with the top text
being diffrent depinding on the setting.

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

[frameworks-kirigami] [Bug 488326] After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message

[Elite]

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

--- Comment #21 from Elite  ---
(In reply to Lunaliz from comment #20)
> I updated my system earlier this morning(Arch Linux), there were some KDE
> updates, and all the problems that I had went away, I am not sure if this
> was the fix or the system fixed itself, the only KDE related update was
> KWin's, so maybe was that? Either way, the bug has been fixed in my machine.
> 
> https://i.imgur.com/FsrIqD4.png
> 
> In this SS, pacman updating kwin from 6.1-01 to 6.1-03 which *might* have
> fixed it.

Can confirm kwin? update seems to have fixed it all it takes is a reboot. an
its fixed.

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

[frameworks-kirigami] [Bug 488326] After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message

[Elite]

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

--- Comment #23 from Elite  ---
(In reply to Claudio from comment #22)
> No not solved with Plasma 6.1 stable or the kwin 6.1-03 package update.
> 
> Please read my 2nd comment: https://bugs.kde.org/show_bug.cgi?id=488326#c3 -
> you first have to click on e.g. "Mouse & Touchpad" -> "Mouse" - than the bug
> triggers - if you first click on any of the problematic pages, than the bug
> does not appear.

just tried that an ya it brought the issue back.

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

[frameworks-kirigami] [Bug 488326] After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message

[Elite]

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

--- Comment #24 from Elite  ---
(In reply to Elite from comment #23)
> (In reply to Claudio from comment #22)
> > No not solved with Plasma 6.1 stable or the kwin 6.1-03 package update.
> > 
> > Please read my 2nd comment: https://bugs.kde.org/show_bug.cgi?id=488326#c3 -
> > you first have to click on e.g. "Mouse & Touchpad" -> "Mouse" - than the bug
> > triggers - if you first click on any of the problematic pages, than the bug
> > does not appear.
> 
> just tried that an ya it brought the issue back.

Logging out an logging back in will restore it to working. it but going to 
mouse will break it.

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

[plasmashell] [Bug 487904] Stuff using Kirigami InlineMessage and PlaceholderMessage fail to load with error `Cannot assign object of type \"Action\" to property of type \"Action_QMLTYPE_72*\" as the

[Elite]

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

Elite  changed:

   What|Removed |Added

 CC||eliteamdgam...@gmail.com

--- Comment #39 from Elite  ---
(In reply to medin from comment #38)
> The QML error is gone after upgrading to Qt 6.7.2

It is still there if you click on mouse an trackpad an then go to a affected
setting. 

Operating System: Garuda Linux (Arch)
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.6-1-cachyos (64-bit)
Graphics Platform: Wayland

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

[kwin] [Bug 489385] New: Moving Windows to virtual desktops results in a hard crash.

[Elite]

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

Bug ID: 489385
   Summary: Moving Windows to virtual desktops results in a hard
crash.
Classification: Plasma
   Product: kwin
   Version: 6.1.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: ---

When you click to drag a window to a virtual desktop. When the setting " Switch
desktop on edge: Only when moving the window". An you drag the window in my
case up or down since im using a ultrawide it makes the most sense.  The system
Will hard lock up.  Requiring a power buton  hold restart. 
>From a little testing I cant reproduce it from an new user. Though in a new
user there is its own bug of not letting you drag the window down it just goes
up. 

1. Have " Switch desktop on edge: Only when moving the window: " set 
2. Have ta least 4 virtual desktops in "individual rows"
3. Drag any window up  to the top  of the screen so it will change Virt
desktops

I've included some poorly taken videos here since I cant use desktop capture to
record the freeze.

Main user:   https://www.youtube.com/watch?v=b0wWSaY5wEQ
New user: https://www.youtube.com/watch?v=BdxAKONiOYI

If there are any other commands I could run to give more info please let me
know. 

Operating System: Garuda Linux 
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.7-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE



```garuda-inxi
System:
  Kernel: 6.9.7-1-cachyos arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cachyos
root=UUID=ed618e85-c1b1-4a62-9eef-7263837ec30d rw rootflags=subvol=@
resume=UUID=9e39bce2-8148-4e68-83a2-8185da8c85fb loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.1.1 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
serial:  part-nu: SKU uuid: 
UEFI: American Megatrends v: 4802 date: 06/15/2023
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701030
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2216 high: 3975 min/max: 550/4426 boost: enabled
scaling: driver: amd-pstate-epp governor: powersave cores: 1: 3975 2: 3973
3: 550 4: 550 5: 3795 6: 550 7: 3686 8: 550 9: 550 10: 3975 11: 3975
12: 550 13: 550 14: 550 15: 3974 16: 3711 bogomips: 115201
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: 
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] vendor: Sapphire
driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm)
built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1
empty: DP-2, HDMI-A-1, HDMI-A-2, Writeback-1 bus-ID: 0c:00.0
chip-ID: 1002:744c class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
  Monitor-1: DP-1 res: 3127x1309 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.0-devel
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 GRE (radeonsi
navi31 LLVM 17.0.6 DRM 3.57 6.9.7-1-cachyos) device-ID: 1002:744c
memory: 15.62 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 12 device: 0 type: discrete-gpu name: AMD
Radeon RX 7900 GRE (RADV NAVI31) driver: mesa radv
v: 24.2.0-devel (git-a3f35964ba) device-ID: 1002:744c
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
17.0.6 256 bits) driver: mesa llvmpipe v: 24.2.0-devel (git-a3f35964ba)
(LLVM 17.0.6) device-ID: 10005: surfaces: xcb,xlib,wayland
Audio:
  Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:ab30
class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0f:0

[plasmashell] [Bug 485471] New: Plasma shell crash

[Elite]

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

Bug ID: 485471
   Summary: Plasma shell crash
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.3)

Qt Version: 6.7.0
Frameworks Version: 6.0.0
Operating System: Linux 6.8.5-1-cachyos x86_64
Windowing System: X11
Distribution: Garuda Linux
DrKonqi: 6.0.3 [CoredumpBackend]

-- Information about the crash:
Upon logging in from any reboot or power on state the shell will crash 1 to 2 
times. Nothing is touched. I thought it was wallpaper engine or a widget i had
but even with them off it still happens. it doesn't  happen on a different
user. At least from my light testing. This was not a issue in 6.0.1

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x705ca63c5ae6 in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x5de06a4dfaf0) at
/usr/src/debug/plasma-workspace/plasma-workspace-6.0.3/applets/kicker/plugin/kastatsfavoritesmodel.cpp:189
#6  QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (arg=, f=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7 
QtPrivate::Functor::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (arg=, f=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:339
#8 
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=0x5de06a4dfae0, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522
#9  0x705cda197609 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb992ace8,
r=0x5de06a58c1d0, this=0x5de06a4dfae0, this=, r=,
a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobjectdefs_impl.h:469


Reported using DrKonqi

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

[plasmashell] [Bug 485471] Plasma shell crash

[Elite]

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

--- Comment #1 from Elite  ---
Created attachment 168443
  --> https://bugs.kde.org/attachment.cgi?id=168443&action=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[plasmashell] [Bug 485762] New: plasmashell crash on startup 6.0.4

[Elite]

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

Bug ID: 485762
   Summary: plasmashell crash on startup 6.0.4
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.4)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.7-1-cachyos x86_64
Windowing System: X11
Distribution: Garuda Linux
DrKonqi: 6.0.4 [CoredumpBackend]

-- Information about the crash:
At boot still receiving a crash 99% of the time after update. I have since shut
off wallpaper engine an non built in widgets an it sill happens in both x11 an
wayland.  I am on garuda arch linux if that helps at all.

The crash can be reproduced every time.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 8927]
[New LWP 8932]
[New LWP 8931]
[New LWP 9066]
[New LWP 8956]
[New LWP 9068]
[New LWP 9069]
[New LWP 9065]
[New LWP 9304]
[New LWP 9074]
[New LWP 9306]
[New LWP 9067]
[New LWP 9267]
[New LWP 9830]
[New LWP 9305]
[New LWP 9075]
[New LWP 9209]
[New LWP 9295]
[New LWP 9316]
[New LWP 9080]
[New LWP 9309]
[New LWP 9328]
[New LWP 9313]
[New LWP 9233]
[New LWP 9320]
[New LWP 9269]
[New LWP 9308]
[New LWP 9240]
[New LWP 9242]
[New LWP 9338]
[New LWP 9314]
[New LWP 9345]
[New LWP 9325]
[New LWP 9327]
[New LWP 10002]
[New LWP 9310]
[New LWP 9317]
[New LWP 9319]
[New LWP 9321]
[New LWP 9323]
[New LWP 9322]
[New LWP 9307]
[New LWP 9318]
[New LWP 9324]
[New LWP 9315]
[New LWP 9831]
[New LWP 9326]
[New LWP 9312]
[New LWP 9311]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x78c1968ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x78c191ee19c0 (LWP 8927))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x78c191ee19c0 (LWP 8927))]

Thread 49 (Thread 0x78c110c006c0 (LWP 9311)):
#0  0x78c1969190df in poll () at /usr/lib/libc.so.6
#1  0x78c195af9306 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x78c195a99712 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x78c197183df4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x78c196f45c7e in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#5  0x78c19702ccef in QThread::run() () at /usr/lib/libQt6Core.so.6
#6  0x78c1970adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#7  0x78c1968a955a in ??? () at /usr/lib/libc.so.6
#8  0x78c196926a5c in ??? () at /usr/lib/libc.so.6

Thread 48 (Thread 0x78c10be006c0 (LWP 9312)):
#0  0x78c1969190df in poll () at /usr/lib/libc.so.6
#1  0x78c195af9306 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x78c195a99712 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x78c197183df4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x78c196f45c7e in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#5  0x78c19702ccef in QThread::run() () at /usr/lib/libQt6Core.so.6
#6  0x78c1970adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#7  0x78c1968a955a in ??? () at /usr/lib/libc.so.6
#8  0x78c196926a5c in ??? () at /usr/lib/libc.so.6

Thread 47 (Thread 0x78c0f2a006c0 (LWP 9326)):
#0  0x78c1969190df in poll () at /usr/lib/libc.so.6
#1  0x78c195af9306 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x78c195a99712 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x78c197183df4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x78c196f45c7e in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#5  0x78c19702ccef in QThread::run() () at /usr/lib/libQt6Core.so.6
#6  0x78c1970adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#7  0x78c1968a955a in ??? () at /usr/lib/libc.so.6
#8  0x78c196926a5c in ??? () at /usr/lib/libc.so.6

Thread 46 (Thread 0x78c0e58006c0 (LWP 9831)):
#0  0x78c1968a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x78c1968a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x78c1970b8b90 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x78c1987f341a in ??? () at /usr/lib/libQt6Quick.so.6
#4  0x78c1970adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x78c1968a9

[dolphin] [Bug 474909] New: Dolphin crash when coping files to fonts folder

[Elite]

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

Bug ID: 474909
   Summary: Dolphin crash when coping files to fonts folder
Classification: Applications
   Product: dolphin
   Version: 23.04.3
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: eliteamdgam...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (23.04.3)

Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.5.5-200.fsync.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: Nobara Linux 38 (KDE Plasma)
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
Was copping the oft fonts from downloads to tthe fonts folder an they would get
hung up at a random pont then stop. then it crashed after 4 ish min of waiting.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x7fea022c5242 in QVector::realloc(int,
QFlags) () from /lib64/libKF5KIOCore.so.5
#5  0x7fea022c8687 in KIO::Connection::send(int, QByteArray const&) () from
/lib64/libKF5KIOCore.so.5
#6  0x7fea02302b99 in KIO::SlaveBase::send(int, QByteArray const&) () from
/lib64/libKF5KIOCore.so.5
#7  0x7fea022fd907 in KIO::SlaveBase::mimeType(QString const&) () from
/lib64/libKF5KIOCore.so.5
#8  0x7fea006e8481 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#9  0x7fe9d8e26b15 in
OrgKdeKioAdminGetCommandInterface::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /usr/lib64/qt5/plugins/kf5/kio/admin.so
#10 0x7fe9d8e26c42 in
OrgKdeKioAdminGetCommandInterface::qt_metacall(QMetaObject::Call, int, void**)
() from /usr/lib64/qt5/plugins/kf5/kio/admin.so
#11 0x7fea019bd38b in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5
#12 0x7fea006ded2b in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7fea013aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#14 0x7fea006b41a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#15 0x7fea006b7655 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#16 0x7fea00706c5f in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#17 0x7fe9fe3134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#18 0x7fe9fe3716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#19 0x7fe9fe310b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#20 0x7fea00706749 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#21 0x7fea006b2b6b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#22 0x7fe9d8e21427 in AdminWorker::get(QUrl const&) () from
/usr/lib64/qt5/plugins/kf5/kio/admin.so
#23 0x7fea02305ee7 in KIO::WorkerSlaveBaseBridge::get(QUrl const&) () from
/lib64/libKF5KIOCore.so.5
#24 0x7fea0230271d in KIO::SlaveBase::dispatch(int, QByteArray const&) ()
from /lib64/libKF5KIOCore.so.5
#25 0x7fea022faa3d in KIO::SlaveBase::dispatchLoop() () from
/lib64/libKF5KIOCore.so.5
#26 0x7fea023784d4 in KIO::WorkerThread::run() () from
/lib64/libKF5KIOCore.so.5
#27 0x7fea004f59dd in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#28 0x7fe9ffeaa8a7 in start_thread () from /lib64/libc.so.6
#29 0x7fe9fff306f4 in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7fe988ff96c0 (LWP 27893) "KIO::WorkerThre"):
#1  0x7fe9fe372420 in sysprof_collector_get () from /lib64/libglib-2.0.so.0
#2  0x7fe9fe372dee in sysprof_collector_mark_vprintf () from
/lib64/libglib-2.0.so.0
#3  0x7fe9fe36971c in g_trace_mark.constprop () from
/lib64/libglib-2.0.so.0
#4  0x7fe9fe3131b4 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#5  0x7fe9fe371491 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#6  0x7fe9fe310b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#7  0x7fea00706766 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#8  0x7fea006b2b6b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#9  0x7fe9d8e2017b in AdminWorker::put(QUrl const&, int,
QFlags) () from /usr/lib64/qt5/plugins/kf5/kio/admin.so
#10 0x7fea0230612e in KIO::WorkerSlaveBaseBridge::put(QUrl const&, int,
QFlags) () from /lib64/libKF5KIOCore.so.5
#11 0x7fea023026d1 in KIO::SlaveBase::dispatch(int, QByteArray const&) ()
from /lib64/libKF5KIOCore.so.5
#12 0x7fea022faa3d in KIO::SlaveBase::dispatchLoop() () from
/lib64/libKF5KIOCore.so.5
#13 0x

[plasmashell] [Bug 485762] plasmashell crash on startup 6.0.4

[Elite]

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

--- Comment #2 from Elite  ---
(In reply to Nate Graham from comment #1)
> Thank you for the bug report! Unfortunately I can't reproduce the crash
> myself on current git master, and the backtrace is incomplete and missing
> debug symbols for the following lines that we need to figure out exactly
> what's going wrong:
> 
> > #4  0x78c16d78a1d6 in ??? () at 
> > /usr/lib/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so
> 
> If you can still reproduce the issue in Plasma 6.1.4 or newer, could you
> please attach a new symbolicated backtrace generated by using `coredumpctl
> gdb` in a terminal window? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
> for details about how to do this.
> 
> Thanks again!

Thankfully I think it was fixed back in 6.1.1. I found at the time changing
kernels stopped it. I've since swapped the kernel back and no issues since
then.

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

[karbon] [Bug 491670] Calligra apps wont open in arch

[Elite]

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

Elite  changed:

   What|Removed |Added

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

--- Comment #1 from Elite  ---
Fixed all issues with the release of Clalligra 4.0

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

[plasma-integration] [Bug 487387] Use of unstyled Qt font selector dialogs constitutes a visual and usability regression

[Elite]

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

Elite  changed:

   What|Removed |Added

 CC||eliteamdgam...@gmail.com

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

[kwin] [Bug 489385] Moving Windows to virtual desktops results in a hard crash.

[Elite]

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

Elite  changed:

   What|Removed |Added

Version|6.1.1   |6.1.2

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

[plasmashell] [Bug 482716] Startup sound does not play

[Elite]

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

Elite  changed:

   What|Removed |Added

 CC||eliteamdgam...@gmail.com

--- Comment #9 from Elite  ---
Having this same issue in 6.1.2  .3 hasn't hit arch yet. but Kde mutes audio
after about 3 seconds. I am using Freedesktop cause I prefer the volume up down
sound on that one. an got a bit tired of replacing the ocean one every update. 

Operating System: Garuda Linux 
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.0-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE

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

[kwin] [Bug 490430] New: Global menu breaks Keepassxc

[Elite]

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

Bug ID: 490430
   Summary: Global menu breaks Keepassxc
Classification: Plasma
   Product: kwin
   Version: 6.1.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: appmenu
  Assignee: kwin-bugs-n...@kde.org
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: ---

***
Global menu not showing for keepassxc. Having global menu enabled prevents keep
pass form generating the menu on the app or at the top of the screen where the
global menu is located. This used to work fine in 2023 an is the same on a new
user. 
***

SUMMARY


STEPS TO REPRODUCE
1. have top panel with global menu 
2. open keepassxc
3.  no menu 
~
4. Close keepassxc fully 
5. remove global menu 
6. open keepassxc 
7. Menu is on the app. 

OBSERVED RESULT
No menu

EXPECTED RESULT
Menu at the top of the screen where the global menu is placed. 

~
Name : keepassxc
Version : 2.7.9-2

Operating System: Garuda Linux 
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.0-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE

ADDITIONAL INFORMATION
Not having it work removes some key features like importing an exporting the
library.
I also added on to a bug report on keepassxc github. The maintainer pointed to
the global menu not working correctly.
https://github.com/keepassxreboot/keepassxc/discussions/10706

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

[plasmashell] [Bug 482716] Startup sound does not play

[Elite]

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

--- Comment #10 from Elite  ---
(In reply to Elite from comment #9)
> Having this same issue in 6.1.2  .3 hasn't hit arch yet. but Kde mutes audio
> after about 3 seconds. I am using Freedesktop cause I prefer the volume up
> down sound on that one. an got a bit tired of replacing the ocean one every
> update. 
> 
> Operating System: Garuda Linux 
> KDE Plasma Version: 6.1.2
> KDE Frameworks Version: 6.4.0
> Qt Version: 6.7.2
> Kernel Version: 6.10.0-1-cachyos (64-bit)
> Graphics Platform: Wayland
> Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
> Memory: 15.5 GiB of RAM
> Graphics Processor: AMD Radeon RX 7900 GRE

~update 7/20/2024 Fixed in 6.1.3

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

[kwin] [Bug 490430] Global menu breaks Keepassxc

[Elite]

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

Elite  changed:

   What|Removed |Added

Version|6.1.2   |6.1.3

--- Comment #1 from Elite  ---
(In reply to Elite from comment #0)
> ***
> Global menu not showing for keepassxc. Having global menu enabled prevents
> keep pass form generating the menu on the app or at the top of the screen
> where the global menu is located. This used to work fine in 2023 an is the
> same on a new user. 
> ***
> 
> SUMMARY
> 
> 
> STEPS TO REPRODUCE
> 1. have top panel with global menu 
> 2. open keepassxc
> 3.  no menu 
> ~
> 4. Close keepassxc fully 
> 5. remove global menu 
> 6. open keepassxc 
> 7. Menu is on the app. 
> 
> OBSERVED RESULT
> No menu
> 
> EXPECTED RESULT
> Menu at the top of the screen where the global menu is placed. 
> 
> ~
> Name : keepassxc
> Version : 2.7.9-2
> 
> Operating System: Garuda Linux 
> KDE Plasma Version: 6.1.2  
> KDE Frameworks Version: 6.4.0
> Qt Version: 6.7.2
> Kernel Version: 6.10.0-1-cachyos (64-bit)
> Graphics Platform: Wayland
> Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
> Memory: 15.5 GiB of RAM
> Graphics Processor: AMD Radeon RX 7900 GRE
> 
> ADDITIONAL INFORMATION
> Not having it work removes some key features like importing an exporting the
> library.
> I also added on to a bug report on keepassxc github. The maintainer pointed
> to the global menu not working correctly.
> https://github.com/keepassxreboot/keepassxc/discussions/10706

~Update~ 7-23-2024 still broken in 6.1.3

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

[NeoChat] [Bug 490796] New: Neochat will not allow user to scroll down after scrolling up for a while.

[Elite]

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

Bug ID: 490796
   Summary: Neochat will not allow user to scroll down after
scrolling up for a while.
Classification: Applications
   Product: NeoChat
   Version: 24.05.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: eliteamdgam...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

***
When scrolling up to check what was said before. When you try to scroll back to
the start it wont let you. it wont go past a post if it has a image or a link.

there is a sweet spot by the users icons to the lft of them about 3 pixels big 
***

SUMMARY


STEPS TO REPRODUCE
1. Open neochat an a group that has a lot of people sharing text an images.
2.  scroll up a ways lets say for 40 seconds 
3. try to scroll back down 

OBSERVED RESULT
Will not scroll down will bounce back up. 

EXPECTED RESULT
scroll s down to where you want 

Operating System: Garuda Linux 
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.0-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE

ADDITIONAL INFORMATION

it is also crashing quite often so i will include that back trace report as
well.

   PID: 488780 (neochat)
   UID: 1000 (elite)
   GID: 1000 (elite)
Signal: 11 (SEGV)
 Timestamp: Wed 2024-07-24 17:19:23 CDT (7min ago)
  Command Line: /usr/bin/neochat
Executable: /usr/bin/neochat
 Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fneochat@8eba17142381451a964cb3b50f925655.service
  Unit: user@1000.service
 User Unit:
app-\x2fusr\x2fbin\x2fneochat@8eba17142381451a964cb3b50f925655.service
 Slice: user-1000.slice
 Owner UID: 1000 (elite)
   Boot ID: 0ba669dd638b4176b8c3fbe54e14b5f7
Machine ID: b9b90682eb2349f0a313d71f01bd75f9
  Hostname: elite-garuda
   Storage:
/var/lib/systemd/coredump/core.neochat.1000.0ba669dd638b4176b8c3fbe54e14b5f7.488780.172185956300.zst
(present)
  Size on Disk: 46.4M
   Message: Process 488780 (neochat) of user 1000 dumped core.

Stack trace of thread 488780:
#0  0x7cd574ca53f4 n/a (libc.so.6 + 0x963f4)
#1  0x7cd574c4c120 raise (libc.so.6 + 0x3d120)
#2  0x7cd57773b643 _ZN6KCrash19defaultCrashHandlerEi
(libKF6Crash.so.6 + 0x6643)
#3  0x7cd574c4c1d0 n/a (libc.so.6 + 0x3d1d0)
#4  0x7cd5753d93b5 _ZNK11QJsonObject5valueE13QLatin1String
(libQt6Core.so.6 + 0x1d93b5)
#5  0x7cd576f3a73b _ZNK8Quotient5Event11contentJsonEv
(libQuotientQt6.so.0.8 + 0x13a73b)
#6  0x55c3956054b4 n/a (neochat + 0x1c14b4)
#7  0x55c3955a73a6 n/a (neochat + 0x1633a6)
#8  0x55c39563a445 n/a (neochat + 0x1f6445)
#9  0x55c39563bb67 n/a (neochat + 0x1f7b67)
#10 0x7cd5774f0a8b n/a (libQt6Qml.so.6 + 0x2f0a8b)
#11 0x7cd5773cd15e n/a (libQt6Qml.so.6 + 0x1cd15e)
#12 0x7cd5773cfe29
_ZNK3QV413QObjectMethod12callInternalEPKNS_5ValueES3_i (libQt6Qml.so.6 +
0x1cfe29)
#13 0x7cd5774195fa n/a (libQt6Qml.so.6 + 0x2195fa)
#14 0x7cd57741d353 n/a (libQt6Qml.so.6 + 0x21d353)
#15 0x7cd577384caf n/a (libQt6Qml.so.6 + 0x184caf)
#16 0x7cd5774195fa n/a (libQt6Qml.so.6 + 0x2195fa)
#17 0x7cd57741d353 n/a (libQt6Qml.so.6 + 0x21d353)
#18 0x7cd577384ab6 n/a (libQt6Qml.so.6 + 0x184ab6)
#19 0x7cd577387c51
_ZN3QV48Function4callEP7QObjectPPvPK9QMetaTypeiPNS_16ExecutionContextE
(libQt6Qml.so.6 + 0x187c51)
#20 0x7cd5774bafc4
_ZN24QQmlJavaScriptExpression8evaluateEPPvPK9QMetaTypei (libQt6Qml.so.6 +
0x2bafc4)
#21 0x7cd57746500f
_ZN25QQmlBoundSignalExpression8evaluateEPPv (libQt6Qml.so.6 + 0x26500f)
#22 0x7cd57746a0bf n/a (libQt6Qml.so.6 + 0x26a0bf)
#23 0x7cd5774dba4c
_ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt6Qml.so.6 +
0x2dba4c)
#24 0x7cd5753a144a n/a (libQt6Core.so.6 + 0x1a144a)
#25 0x7cd572aab82b n/a (libQt6QuickTemplates2.so.6 +
0xab82b)
#26 0x7cd572ab11ff
_ZN12QQuickAction11qt_metacallEN11QMetaObject4CallEiPPv
(libQt6QuickTemplates2.so.6 + 0xb11ff)
#27 0x7cd5774f0a8b n/a (libQt6Qml.so.6 + 0x2f0a8b)
#28 0x7cd5773cc4f2 n/a (libQt6Qml.so.6 + 0x1cc4f2)
#29 0x7cd5773cfe29

[frameworks-knewstuff] [Bug 484057] Can't upgrade plasma plasmoid from get new window

[Elite]

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

Elite  changed:

   What|Removed |Added

 CC||eliteamdgam...@gmail.com

--- Comment #9 from Elite  ---
Same on arch.

Operating System: Garuda Linux 
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.3-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE

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

[karbon] [Bug 491670] New: Calligra apps wont open in arch

[Elite]

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

Bug ID: 491670
   Summary: Calligra apps wont open in arch
Classification: Applications
   Product: karbon
   Version: 3.2.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ja...@gmx.net
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: ---

Created attachment 172585
  --> https://bugs.kde.org/attachment.cgi?id=172585&action=edit
How the bug looks with no menu bar

Opening any calligra app results in the following error, 

```
❯ karbon
QFont::fromString: Invalid description 'Inter
Variable,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1'
QFont::fromString: Invalid description 'Hack Nerd Font
Mono,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1'
QFont::fromString: Invalid description 'Inter
Variable,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1'
QFont::fromString: Invalid description 'Inter
Variable,8,-1,5,400,0,0,0,0,0,0,0,0,0,0,1'
calligra.lib.migration: kde home not found
20 -- exe=/usr/bin/karbon
17 -- platform=wayland
15 -- appname=karbon
17 -- apppath=/usr/bin
10 -- signal=11
11 -- pid=126278
17 -- appversion=3.2.1
19 -- programname=Karbon
31 -- bugaddress=sub...@bugs.kde.org
19 -- productname=karbon
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = karbon path = /usr/bin pid = 126278
KCrash: Arguments: /usr/bin/karbon 
The Wayland connection experienced a fatal error: Bad file descriptor
```
However installing it on a distrobox arch instance it works but it wont export
the menu to the global menu so its not a great solution.  As not having file,
edit, view etc leaves some features on the table.  

Also wont show in the crash viewer. but i think that in itself has another bug
going on with it. 

SUMMARY
Will not open on arch main install but will open in a distrobox made with arch. 

STEPS TO REPRODUCE
1. install calligra from arch extra repo
2. type karbon in terminal 

OBSERVED RESULT
provides the error above. When just clicking on the icon it silent crashes. 

EXPECTED RESULT
open karbon 

SOFTWARE/OS VERSIONS
System:
  Kernel: 6.10.4-1-cachyos arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cachyos
root=UUID=ed618e85-c1b1-4a62-9eef-7263837ec30d rw rootflags=subvol=@
resume=UUID=9e39bce2-8148-4e68-83a2-8185da8c85fb loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A info: frameworks v: 6.4.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
serial:  part-nu: SKU uuid: 
UEFI: American Megatrends v: 4802 date: 06/15/2023
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701030
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2731 high: 3947 min/max: 550/4426 boost: enabled
scaling: driver: amd-pstate-epp governor: powersave cores: 1: 3862 2: 3808
3: 550 4: 550 5: 3566 6: 3947 7: 3718 8: 3912 9: 550 10: 3599 11: 3926
12: 3599 13: 3490 14: 550 15: 550 16: 3530 bogomips: 115201
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: 
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] vendor: Sapphire
driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm)
built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1
empty: DP-2, HDMI-A-1, HDMI-A-2, Writeback-1 bus-ID: 0c:00.0
chip-ID: 1002:744c class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
  Monitor-1: DP-1 res: 3127x1309 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.0-devel
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 GRE (radeonsi
navi31 LLVM 18.1.8 DRM 3.57 6.10.4-1-cachyos) device-ID: 1002:744c
memory: 15.62 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon RX 7900 GRE (RADV NAVI31) driver: mesa radv
v: 24.3.0-devel (git-dd5cce4730) device-ID: 1002:744c
surfaces: xcb,xlib,wayland device: 1 type: discrete-gpu
name: AMD Radeon RX 7900 GRE driver: amd v: (LLPC) device-ID: 1002:744c
surfaces: xcb,xlib,wa

[kwin] [Bug 489385] Moving Windows to virtual desktops results in a hard crash.

[Elite]

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

Elite  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Elite  ---
(In reply to Vlad Zahorodnii from comment #1)
> I cannot reproduce the issue. Can you check kwin's logs when the hard freeze
> occurs? 
> 
>   journalctl --boot --user-unit plasma-kwin_wayland > log.txt
> 
> also, is there any chance that you could retrieve kwin's backtrace when the
> hard freeze occurs? You would need to ssh from another computer and attach a
> debugger to kwin process, e.g.
> 
>   sudo gdb -p $(pidof kwin_wayland)
> 
> then type
> 
>   bt
> 
> and paste the output here
> 
> https://community.kde.org/KWin/Debugging contains more details

It seems to have been fixed since 6.2. If the bug comes back ill report it
again. With the journal and backtrace if i can manage that one.

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

[plasmashell] [Bug 498175] Desktop goes black and panels disappear when changing the global theme with "Desktop and window layout selected", until plasmashell is restarted

[Elite]

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

Elite  changed:

   What|Removed |Added

 CC||eliteamdgam...@gmail.com

--- Comment #14 from Elite  ---
The bug is also in 6.4 dev.  Wayland on a amd 7900. With KDEOS

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

[Discover] [Bug 498902] New: Discover Not Updating Plasma-Addons

[Elite]

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

Bug ID: 498902
   Summary: Discover Not Updating Plasma-Addons
Classification: Applications
   Product: Discover
   Version: master
  Platform: NixOS
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Updates (interactive)
  Assignee: plasma-b...@kde.org
  Reporter: eliteamdgam...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 177534
  --> https://bugs.kde.org/attachment.cgi?id=177534&action=edit
Picture of Discover not showing what needs updated, while Get-New icons shows
things that can be updated. With a bit of the terminal ouput thats posted
below.

***
In  both nixos and arch on the latest stable kde builds Discover won't update
plasma addons. 
***

SUMMARY
In discover it will let you download addons just fine but will never ask you to
update them to do so you have to go to the Get New section of there that icon
or theme is from. That fails sometimes as well lately but that needs its own
bug report. 

In terminal when opening discover for the first time it shows its looking an
sees the addons. 

STEPS TO REPRODUCE
1. Install some icons or theme parts with git new.
2. See that one needs a update (Ars-Dark-Icons are updated often)
3. Open discover an check for updates by refreshing the list.

OBSERVED RESULT
Nothing to be updated other then maybe flatpaks that day. 

EXPECTED RESULT
Show addons to be updated. (Same thing happens when you install a addon
directly from discover.)

SOFTWARE/OS VERSIONS
Operating System: NixOS 25.05
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE

ADDITIONAL INFORMATION
Some Terminal Output:

cache entry KNSCore::Entry(uniqueId: "2112373", name:"Infinity Glass Icon
Theme", status: Installed, installedFiles:
QList("/home/elite/.local/share/icons/Infinity/*")) "0.2.9" "0.3.2"
looking for cache entry
looking for cache entry 18
cache entry KNSCore::Entry(uniqueId: "2104775", name:"DeepMacOS IconTheme",
status: Installed, installedFiles:
QList("/home/elite/.local/share/icons/DeepMacOS-IconTheme/*")) "" ""
looking for cache entry
looking for cache entry 19
cache entry KNSCore::Entry(uniqueId: "1217074", name:"Oxygen Classic [KDE
4.6.2]", status: Installed, installedFiles:
QList("/home/elite/.local/share/icons/oxygen-icons-4.6.2/*")) "" ""
looking for cache entry
looking for cache entry 22
cache entry KNSCore::Entry(uniqueId: "2152387", name:"Nature Icon Theme - KDE",
status: Installed, installedFiles: QList("/home/elite/.local/share/icons/Nature
- Blue - KDE/*")) "1.3" "1.4"
looking for cache entry
looking for cache entry 21
cache entry KNSCore::Entry(uniqueId: "2180417", name:"Aretha-Dark-Icons",
status: Installed, installedFiles:
QList("/home/elite/.local/share/icons/Aretha-Dark-Icons/*")) "" ""
looking for cache entry
looking for cache entry 16
cache entry KNSCore::Entry(uniqueId: "2049257", name:"Fekete", status:
Installed, installedFiles: QList("/home/elite/.local/share/icons/Fekete/*"))
"2" "2"
looking for cache entry
looking for cache entry 12
cache entry KNSCore::Entry(uniqueId: "1160037", name:"Oxygen Remixed Icons",
status: Installed, installedFiles:
QList("/home/elite/.local/share/icons/oxygen-mix-1.4/*")) "1.4" "1.4"
looking for cache entry
looking for cache entry 15
cache entry KNSCore::Entry(uniqueId: "1733012", name:"Nordic folders", status:
Installed, installedFiles:
QList("/home/elite/.local/share/icons/Nordic-bluish/*",
"/home/elite/.local/share/icons/Nordic-darker/*",
"/home/elite/.local/share/icons/Nordic-green/*")) "" ""
looking for cache entry
looking for cache entry 17
cache entry KNSCore::Entry(uniqueId: "2150463", name:"Besgnulinux Colors",
status: Installed, installedFiles:
QList("/home/elite/.local/share/icons/besgnulinux-colors/*")) "" ""
looking for cache entry
looking for cache entry 11
cache entry KNSCore::Entry(uniqueId: "2188927", name:"Palette-icon-theme",
status: Installed, installedFiles:
QList("/home/elite/.local/share/icons/Palette-Adwaita-Dark/*",
"/home/elite/.local/share/icons/Palette-Adwaita/*",
"/home/elite/.local/share/icons/Palette-Adwaita-Light/*")) "1.2" "1.2&

[Discover] [Bug 501953] New: [Feature Request] Clean up error screen

[Elite]

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

Bug ID: 501953
   Summary: [Feature Request] Clean up error screen
Classification: Applications
   Product: Discover
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: eliteamdgam...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 179705
  --> https://bugs.kde.org/attachment.cgi?id=179705&action=edit
Error message.

Is there anyway the error prompt could be cleaned up a bit? 
Maybe if it is a error for a kde app, if there is ever one. It will bring up
the bug tracker?  The one where it asks for more info on what you are doing to
send a bug report. Or brings you to kde bugs with the system info and bug
report filled in to a degree. Then asks for more info. 
For 3rd party maybe it could be more simple with a link to the git hub/lab.
Like I understand what the error talking about but I know non tech user would
not. Like not knowing what to do with the "copy to clipboard" There is the
dialog before "There was an issue during the update or installation process.
Please try again later" but that could be confusing on if anything actually
finished installing that didn't fail. 
And if it happens more often they might/will click the "See Technical Details"
copy paste it into a browser an wont get any useful information. 

At the least having it say X Y and Z failed but everything else was updated
might be useful.

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

[kwin] [Bug 501871] [Feature request] Global menu enabled removes hamburger menu on kde apps

[Elite]

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

Elite  changed:

   What|Removed |Added

   Keywords||accessibility

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

[frameworks-kconfigwidgets] [Bug 501871] Global menu being enabled should remove hamburger menu button

[Elite]

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

--- Comment #3 from Elite  ---
(In reply to Felix Ernst from comment #2)
> (In reply to Nate Graham from comment #1)
> > Yeah, it makes sense to only have one menu structure visible, not two. This
> > is the reason why we automatically hide the hamburger menu button when the
> > in-window menubar is visible.
> > 
> > In QtWidgets apps, we could make KHamburgerMenu hide itself when it detects
> > a global menu.
> 
> It used to be that way, but we actively changed this in
> https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/46 and
> received far fewer complaints since then. I think the current state is way
> better on average than hiding KHamburgerMenu when a global menu exists. So I
> think we need a different solution.

Perhaps this could just be a option in settings the user can enable or disable.
As that would solve most of if not the full request. 

> (In reply to Elite from comment #0)
> > I manage quite a few users in several places in the US. that have limited or
> > no mobility and navigate the system with their eyes, mouth, or sometimes a
> > vary shaky finger. While most can see fine some do not. 
> > 
> > I'm requesting a setting  that can be toggled or some other way that when a
> > global menu is present it removes hamburger buttons from kde apps that it
> > can be.Ardour
> 
> Is the mere existence of the hamburger button a big problem? I understand
> that it is annoying having to manually remove it from every application, but
> I am trying to identify the core issue of this bug report. I would assume
> ignoring the button is not that big of an issue because many UIs have
> buttons that the user does not care about.

Most of the users I'm talking about in this request have challenges. Let's say
the wallpaper changes from blue to green it end up with the nurse being called.
Most are X mac users. So I set up most everything as closely as possible and
remove anything that causes a stir. I personally can't be around every user
every time they add something. The main goal is to keep everything other then
the browser KDE it's easier to maintain. I also can not reliably expect a user
who's use of right click depends on a blink sequence that is quite unreliable
to manually remove it from every app.
But yes the sight of it affects some. It's no fault of the user it's just how
they are. 

> > Or that when the hamburger button is removed at least after a
> > restart it would generate the options in the global menu. 
> 
> There might be a misunderstanding there. Hiding the hamburger button has no
> effect on what shows up in global menus. If a global menu does not show all
> options of an application, that is because those applications do not export
> their menu structure to the global menu.
> 
> You are probably experiencing this issue mostly with more recently invented
> KDE applications, right? Those are Kirigami applications and many of them
> have hamburger buttons but do not export a global menu structure.
The only Kirigami app I have seen like that I think would be tokodon? At the
least none of the users I've interacted with have had that on their system. 
> > Why, 
> >   when your way of movement is you have to look at a point to move the
> > mouse. look at one point for long time to right click. When it's in one area
> > that stays the same you can map things to make it far easier to use.
> > Hamburger menus or buttons on apps can't really be mapped with that in mind
> > since they can always be in different places.
> 
> I am not sure if this helps, but I actually added a generic keyboard
> shortcut for opening the menu. Pressing F10 in applications that use
> KHamburgerMenu should either open the hamburger menu if it is visible, or
> open the first in-application menu bar menu. This has been changed one and a
> half years ago in
> https://invent.kde.org/frameworks/kconfig/-/merge_requests/222. If an
> application does not support that, it can be considered an application bug.
> 
> I am currently not sure if I fully understood the issue we are trying to fix
> here. Elite, if it seems like we are talking past each other, please let me
> know. We might need more context to identify the best path forward.

I can't really map shortcuts for them as they are mostly paralyzed from the
neck down. The other issue is the menus not really coherent. Less shown is not
better in this case.  The equivalent of "Edit"  "Actions for current view"  is
just honestly not clear and is a bit to complicated for some.

What I think would help is a button in settings that can be used to shut off
the hamburger menu for the kde apps that need it like Dolphin for example. When
the global menu is activated.

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

[frameworks-kconfigwidgets] [Bug 501871] Global menu being enabled should remove hamburger menu button

[Elite]

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

--- Comment #8 from Elite  ---
I'm not sure if this is the correct platform. But maybe a more simple solution
in the full linux space is give it a better icon not just in kde but in the
other toolkits as well. If removing it is difficult maybe a shift in giving it
a icon that makes since to what its function represents would be better.  I'm
not sure what that would look like but the three - lines, don't really
represent what your clicking on. Nor do they show that you generally are
getting fewer options or that more options are hidden in more drop-downs. 


I cant say this is a solution but if hiding it with a toggle or some code
that's aware the user is using normal menus/global menus can't really be done
in a economical way that doesn't put stress on the kde developers. Maybe
changing how it looks to something more representative to its actual function
would be better. I know web wont use a standard like that. But maybe the kde
and gtk side could. Though I know its a stretch.

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

[systemsettings] [Bug 503341] New: [Feature Request] Expose OpenType font features to user [Accessibility]

[Elite]

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

Bug ID: 503341
   Summary: [Feature Request] Expose OpenType font features to
user [Accessibility]
Classification: Applications
   Product: systemsettings
   Version: master
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_fonts
  Assignee: plasma-b...@kde.org
  Reporter: eliteamdgam...@gmail.com
CC: ritc...@kde.org
  Target Milestone: ---

Created attachment 180642
  --> https://bugs.kde.org/attachment.cgi?id=180642&action=edit
Image from font forge show how naming is done.

My request is for exposing the basic opentype features of a font to the user,
allowing the user to turn on and off the features. Would greatly help with
accessibility, for dyslexia or vision impermanent. Though the font has to
provide these changes. 
My example is the Inter font https://rsms.me/inter/ I use the setting ss02 for
changing uppercase i so it is different from lower case L. It's also useful if
the font supports fractions or fixed-width numbers. For me at least the current
popular dyslexic fonts just make text far harder to read so just by tweaking
these few setting make all the difference. 

In fontforge, mind you it does not work for changing these settings. (Spent 5
hours trying to.) You go to Element -> Font Info -> StyleSet Names an it gives
the language, feature # and the "friendly name" As shown in the attachment. 
You can also go to Element -> Font Info -> Lookups and get far more data about
it an what it changes though its quite cryptic and not user friendly. 

There is also the CLI tool fonttools-opentype-feature-freezer
https://twardoch.github.io/fonttools-opentype-feature-freezer/ but its
basically not functional in a sandbox environment often not allowing you to
give the fonts location when in the folder containing it an giving a absolute
path. Or working well when the font has multiple variations in one .ttc file. 

The way i see this working is it exposes the ss## and cv##  with the numbers an
what the font provides as a human definition of that function. an the user can
pick via a check box or save the font with a different name they chose with the
changes made. I feel this would fit under font management maybe in its own
tab/menu. But anything works. 
There is no real rush to get this done it however would be nice around the time
plasma 7 comes.


As per the matrix request here
https://matrix.to/#/!mKemwTajwjZEayOyXO:kde.org/$rWVCDcNev5EFh_1p7apHxrxEGpmrt8m1AErblv2JvMo
I am tagging Ritchie

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

[frameworks-kconfigwidgets] [Bug 501871] Global menu being enabled should remove hamburger menu button

[Elite]

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

--- Comment #12 from Elite  ---
I think I have the answer, so this issue can most likely be closed. I don't
think linux in general will be a great fit for these users. I don't personally
see a future where UX functionality is brought back into the use case over
minimalism. Many want this touch friendly minimalism that's just not applicable
to some users with motor skill / mental impairments. At no fault to KDE or
anyone else. 
I thank you all for taking the time to hear me out though.

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

[plasmashell] [Bug 499914] Fit-content plasma panel doesn't shrink back when Task Manager tasks disappear

[Elite]

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

Elite  changed:

   What|Removed |Added

 CC||eliteamdgam...@gmail.com

--- Comment #12 from Elite  ---
Can be replicated on Nixos as well. In both wayland and x11.
https://youtu.be/trT1DOfTD1w

System:
  Kernel: 6.13.2-cachyos arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters:
initrd=\EFI\nixos\vnzphbamwg03sapz3wd1ibmfp1h86dk3-initrd-linux-6.13.2-initrd.efi
   
init=/nix/store/f5dxqnzmhv2vfcl6syf0hjy5skjkwyl2-nixos-system-nixos-25.05.20250216.d74a233/init
psi=1 loglevel=4
  Desktop: KDE Plasma v: 6.3.0 tk: Qt v: N/A info: frameworks v: 6.10.0
wm: kwin_wayland with: docker,krunner vt: 2 dm: SDDM
Distro: NixOS 25.05 (Warbler)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
serial:  part-nu: SKU uuid: 
UEFI: American Megatrends v: 5013 date: 03/22/2024
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701034
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 3953 high: 4357 min/max: 550/4426 boost: enabled
scaling: driver: amd-pstate-epp governor: performance cores: 1: 4349 2:
4349
3: 4350 4: 3935 5: 4350 6: 1757 7: 4357 8: 4350 9: 4349 10: 4347 11: 4350
12: 4351 13: 4348 14: 4349 15: 3606 16: 1757 bogomips: 115196
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: 
Graphics:
  Message: Required tool lspci not installed. Check --recommends
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5
compositor: kwin_wayland driver: N/A display-ID: 0 screens: 1
  Screen-1: 0 s-res: 3440x1440 s-size: 
  Monitor-1: DP-1 res: 3440x1440 hz: 144 dpi: 109
size: 800x335mm (31.5x13.19") diag: 867mm (34.15") modes: N/A
  API: Vulkan Message: No Vulkan data available.
  API: EGL Message: EGL data requires eglinfo. Check --recommends.

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

[kwin] [Bug 501871] New: [Feature request] Global menu enabled removes hamburger menu on kde apps

[Elite]

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

Bug ID: 501871
   Summary: [Feature request] Global menu enabled removes
hamburger menu on kde apps
Classification: Plasma
   Product: kwin
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: ---

I manage quite a few users in several places in the US. that have limited or no
mobility and navigate the system with their eyes, mouth, or sometimes a vary
shaky finger. While most can see fine some do not. 

I'm requesting a setting  that can be toggled or some other way that when a
global menu is present it removes hamburger buttons from kde apps that it can
be. Or that when the hamburger button is removed at least after a restart it
would generate the options in the global menu. 

Why, 
  when your way of movement is you have to look at a point to move the mouse.
look at one point for long time to right click. When it's in one area that
stays the same you can map things to make it far easier to use. Hamburger menus
or buttons on apps can't really be mapped with that in mind since they can
always be in different places. 
The issue that they tell me is "Why is it not in the same place. Why are
options buried in sub menus. How do I change it back or to fit me"   

So having a toggle or having the app be aware that when its present would be
useful. I am aware 3rd party apps will not follow this but their usage can be
kept to a minimum. 

I'm not asking to stop changing the ux as you are but, having this as a
accessibility option would solve a lot of issues when things do change. 

My apologies if this is in the wrong area.

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

[kwin] [Bug 504647] DP 1.4 set to 144hz cause white lines in wayland

[Elite]

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

--- Comment #1 from Elite  ---
(In reply to Elite from comment #0)
> SUMMARY
> When the display is set to its default resolution and refresh rate it cause
> white lines similar to old static. this also happens in the SDDM and then
> things are set to default breeze. Changing DP results in the same problem.
> This does not happen when on the same system from the sddm logging into
> another DE. Or even if they are all fully removed.  I have also tried
> another monitor of the same make and model and same gpu make and model. All
> give the same result. 
> I did notice that it happens in the sddm if I log out. 
> It manly happens when there any  movement on screen moving a mouse moving a
> blinking terminal courser. When dragging a window back an forth it doesn't
> seem to happen tell the window stops moving. It used to be fixed for a while
> by setting any other refresh rate not saving and going back to 144hz. I cant
> capture it on video either. its almost like screen tearing or vsync is
> having some issue. I have adaptive sync fully disabled on the monitor as
> well. 
> 
> If the monitor is set to DP 1.2, it no longer happens but the display can no
> longer hit its default refresh rate so everything  looks choppy. 
> I don't remember this happening in 6.3.2.
> 
> STEPS TO REPRODUCE
> 1. Make sure the monitor supports DP 1.4 set refresh rate to 144hz or
> higher. 
> 2. open a video played from a local file or a long config in kate 
> 3. play or scroll the text file.
> 
> OBSERVED RESULT
> White Lines randomly over the display.
> 
> EXPECTED RESULT
> no lines 
> 
> SOFTWARE/OS VERSIONS
> Operating System: NixOS 25.11
> KDE Plasma Version: 6.3.5
> KDE Frameworks Version: 6.14.0
> Qt Version: 6.9.0
> Kernel Version: 6.14.7-cachyos (64-bit)
> Graphics Platform: Wayland
> Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
> Memory: 31.2 GiB of RAM
> Graphics Processor: AMD Radeon RX 7900 GRE
> 
> ADDITIONAL INFORMATION
> 
> System:
>   Kernel: 6.14.7-cachyos arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
> clocksource: tsc avail: hpet,acpi_pm
> parameters:
> initrd=\EFI\nixos\1y87izfnn4ayic3n47x2y45s5fqajx0w-initrd-linux-6.14.7-
> initrd.efi
>
> init=/nix/store/hnvax2y675x99bfihsmc9vmasgg868l3-nixos-system-nixos-25.11.
> 20250520.2795c50/init
> quiet splash rd.systemd.show_status=false rd.udev.log_level=3
> udev.log_priority=3 loglevel=3 plymouth.force-splash boot.shell_on_fail
> psi=1 splash loglevel=0
>   Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
> wm: kwin_wayland vt: 4 dm: SDDM Distro: NixOS 25.11 (Xantusia)
> Machine:
>   Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
> serial:  part-nu: SKU uuid: 
> UEFI: American Megatrends v: 5031 date: 01/13/2025
> CPU:
>   Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 2
> level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
> family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701035
>   Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
> smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
> desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
>   Speed (MHz): avg: 4261 min/max: 560/4427 boost: enabled scaling:
> driver: amd-pstate-epp governor: performance cores: 1: 4261 2: 4261 3:
> 4261
> 4: 4261 5: 4261 6: 4261 7: 4261 8: 4261 9: 4261 10: 4261 11: 4261 12:
> 4261
> 13: 4261 14: 4261 15: 4261 16: 4261 bogomips: 115197
>   Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
>   Vulnerabilities: 
> Graphics:
>   Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900
> XTX/7900 GRE/7900M] vendor: Sapphire driver: amdgpu v: kernel arch:
> RDNA-3
> code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4
> speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2, HDMI-A-1,
> HDMI-A-2, Writeback-1 bus-ID: 0d:00.0 chip-ID: 1002:744c class-ID: 0300
>   Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
> compositor: kwin_wayland driver: gpu: amdgpu display-ID: 0
>   Monitor-1: DP-1 model: LG (GoldStar) ULTRAGEAR serial: 
> built: 2020 res: 3440x1440 dpi: 109 gamma: 1.2 size: 800x335mm
> (31.5x13.19")
> diag: 867mm (34.1") modes: max: 3440x1440 min: 640x480
>   API: Vulkan Message: No Vulkan data available.
>   API: EGL Message: EGL data requires eglinfo. Check --recommends.
>   Info: Tools: api: clinfo,vulkaninfo de: kscreen-console,kscreen-doctor
> gpu: lact x11: xprop,xrandr
> Audio:
>   Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Aud

[kwin] [Bug 504647] New: DP 1.4 set to 144hz cause white lines in wayland

[Elite]

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

Bug ID: 504647
   Summary: DP 1.4 set to 144hz cause white lines in wayland
Classification: Plasma
   Product: kwin
  Version First 6.3.5
   Reported In:
  Platform: NixOS
OS: Linux
Status: REPORTED
  Keywords: wayland-only
  Severity: major
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: eliteamdgam...@gmail.com
  Target Milestone: ---

SUMMARY
When the display is set to its default resolution and refresh rate it cause
white lines similar to old static. this also happens in the SDDM and then
things are set to default breeze. Changing DP results in the same problem. This
does not happen when on the same system from the sddm logging into another DE.
Or even if they are all fully removed.  I have also tried another monitor of
the same make and model and same gpu make and model. All give the same result. 
I did notice that it happens in the sddm if I log out. 
It manly happens when there any  movement on screen moving a mouse moving a
blinking terminal courser. When dragging a window back an forth it doesn't seem
to happen tell the window stops moving. It used to be fixed for a while by
setting any other refresh rate not saving and going back to 144hz. I cant
capture it on video either. its almost like screen tearing or vsync is having
some issue. I have adaptive sync fully disabled on the monitor as well. 

If the monitor is set to DP 1.2, it no longer happens but the display can no
longer hit its default refresh rate so everything  looks choppy. 
I don't remember this happening in 6.3.2.

STEPS TO REPRODUCE
1. Make sure the monitor supports DP 1.4 set refresh rate to 144hz or higher. 
2. open a video played from a local file or a long config in kate 
3. play or scroll the text file.

OBSERVED RESULT
White Lines randomly over the display.

EXPECTED RESULT
no lines 

SOFTWARE/OS VERSIONS
Operating System: NixOS 25.11
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.7-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE

ADDITIONAL INFORMATION

System:
  Kernel: 6.14.7-cachyos arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters:
initrd=\EFI\nixos\1y87izfnn4ayic3n47x2y45s5fqajx0w-initrd-linux-6.14.7-initrd.efi
   
init=/nix/store/hnvax2y675x99bfihsmc9vmasgg868l3-nixos-system-nixos-25.11.20250520.2795c50/init
quiet splash rd.systemd.show_status=false rd.udev.log_level=3
udev.log_priority=3 loglevel=3 plymouth.force-splash boot.shell_on_fail
psi=1 splash loglevel=0
  Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
wm: kwin_wayland vt: 4 dm: SDDM Distro: NixOS 25.11 (Xantusia)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
serial:  part-nu: SKU uuid: 
UEFI: American Megatrends v: 5031 date: 01/13/2025
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 2
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701035
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 4261 min/max: 560/4427 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 4261 2: 4261 3: 4261
4: 4261 5: 4261 6: 4261 7: 4261 8: 4261 9: 4261 10: 4261 11: 4261 12: 4261
13: 4261 14: 4261 15: 4261 16: 4261 bogomips: 115197
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: 
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900
XTX/7900 GRE/7900M] vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-3
code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2, HDMI-A-1,
HDMI-A-2, Writeback-1 bus-ID: 0d:00.0 chip-ID: 1002:744c class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: gpu: amdgpu display-ID: 0
  Monitor-1: DP-1 model: LG (GoldStar) ULTRAGEAR serial: 
built: 2020 res: 3440x1440 dpi: 109 gamma: 1.2 size: 800x335mm
(31.5x13.19")
diag: 867mm (34.1") modes: max: 3440x1440 min: 640x480
  API: Vulkan Message: No Vulkan data available.
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: clinfo,vulkaninfo de: kscreen-console,kscreen-doctor
gpu: lact x11: xprop,xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-I

[NeoChat] [Bug 504625] New: [Wishlist] Screenshot Privacy Mode

[Elite]

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

Bug ID: 504625
   Summary: [Wishlist] Screenshot Privacy Mode
Classification: Applications
   Product: NeoChat
  Version First unspecified
   Reported In:
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: eliteamdgam...@gmail.com
CC: c...@carlschwan.eu, j...@redstrate.com
  Target Milestone: ---

Created attachment 181619
  --> https://bugs.kde.org/attachment.cgi?id=181619&action=edit
64gram version of screenshot mode

Having a toggle to trigger a screenshot mode preferably in the menu/global
menu. Where it gives a generic output for whats shown fore
severs/rooms/chats/user names. Could be useful for sharing images as well as
reporting bugs when you or the other party don't really want their info
exposed. I've attached a photo for how it looks in 64gram. Though unlike
neochat it might be useful for it to rename the room name above the chat
window. Such as when in the NeoChat room at the top it gives a generic name for
NeoChat

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