Confirmed on:

  Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917
    class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.10 with: Xwayland v: 23.2.3
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast surfaceless: drv: iris wayland: drv: iris x11:
    drv: iris inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.3.3-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 620 (KBL
    GT2) device-ID: 8086:5917 memory: 3.62 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.3.274 layers: N/A device: 0 type: integrated-gpu
    name: Intel UHD Graphics 620 (KBL GT2) driver: mesa intel v: 23.3.3-arch1.1
    device-ID: 8086:5917 surfaces: xcb,xlib,wayland

Operating System: EndeavourOS 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0

Nico confirmed this with Qt 6.7 but not Arch, so probably not an Arch packaging issue.

*** Bug 479428 has been marked as a duplicate of this bug. ***

On my system (kde-unstable w Qt 6.7), the Get New Fonts button DOES work. But the rest are broken.

In addition, there are two other buttons in systemsettings that don't work:
- the Add button in the Autostart section
- the Add New button in the Shortcuts section

Can confirm, using Plasma 6.0 RC1 on arch. 'Get New' button for themes still not working as of 2024-1-17, only works for fonts.

This is https://bugreports.qt.io/browse/QTBUG-121197

*** Bug 480854 has been marked as a duplicate of this bug. ***

*** Bug 481168 has been marked as a duplicate of this bug. ***

*** Bug 481521 has been marked as a duplicate of this bug. ***

Git commit 4f01e2ff676cd4a11ba36f49d967db4635e2d216 by Nicolas Fella.
Committed on 07/03/2024 at 18:55.
Pushed by nicolasfella into branch 'master'.

[qtquick/action] Add API to set transient parent for dialog

We want the dialog to have a proper parent window set. Usually
Qt automatically obtains one from the parent item. This doesn't
work here however since the dialog's loader is not part of the item
hierarchy. This causes the window to not be shown since Qt 6.7.

See QTBUG-121197

Merely adding the property and setting it to null makes sure the
window can be shown. Users of the API should however pass a parent window
so that the dialog has a parent set.

M  +9    -0    src/qtquick/qml/Action.qml

https://invent.kde.org/frameworks/knewstuff/-/commit/4f01e2ff676cd4a11ba36f49d967db4635e2d216

*** Bug 485392 has been marked as a duplicate of this bug. ***

*** Bug 485392 has been marked as a duplicate of this bug. ***

👆️ Duplicate or not this issue has regressed. As of now I have all updates applied on KDE Neon, and the following "Get New" buttons do nothing when I attempt to use them:
- Icons
- Colors
- Plasma Style
- Window Decorations
- Cursors
- Splash Screens
- Login Screen (SDDM)
- Boot Splash Screen

In other words, all of them.

(In reply to William Hood from comment #12)
> *** Bug 485392 has been marked as a duplicate of this bug. ***
> 
> 👆️ Duplicate or not this issue has regressed. As of now I have all updates
> applied on KDE Neon, and the following "Get New" buttons do nothing when I

FIXED means fixed in KDE. If your distribution still doesn't ship the fix, you need to wait for it.

> FIXED means fixed in KDE. If your distribution still doesn't ship the fix, you need to wait for it.

Yes, I understand that. I'd like to think that KDE Neon, developed by KDE, is about as up-to-date as KDE gets. This is not an issue that's been present since January 14'th all this time, this is something that was working fine until just a few days ago and then suddenly broke. Either this bug regressed, or it's a brand new bug that just happens to have the same symptoms.

(In reply to William Hood from comment #14)
> Yes, I understand that. I'd like to think that KDE Neon, developed by KDE,
> is about as up-to-date as KDE gets. This is not an issue that's been present
> since January 14'th all this time, this is something that was working fine
> until just a few days ago and then suddenly broke. Either this bug
> regressed, or it's a brand new bug that just happens to have the same
> symptoms.

As the bug title clearly states, this happens with Qt 6.7. So you did not experience the bug until your distribution updated to that Qt version.

> As the bug title clearly states, this happens with Qt 6.7. So you did not
> experience the bug until your distribution updated to that Qt version.

Thank you for clarifying