There are developers who are looking for further clarifications and improvements.
Example:
2026-06-18: Session management with Qt
The title of this thread is āKDE Plasma 6.7 with crashing componentsā and all Iām saying is that I do not have any crashing components on my system (openSUSE Tumbleweed 20260618 Plasma 6.7).
2 Likes
Further software adjustments were applied here a moment ago.
Markus_Elfring@Sonne:~> rpm -qi plasma6-desktop xdg-desktop-portal-kde6 kscreen6
ā¦
Source RPM : plasma6-desktop-6.7.1-1.1.src.rpm
Build Date : Di 23 Jun 2026 13:00:14 CEST
ā¦
Source RPM : xdg-desktop-portal-kde6-6.7.1-1.1.src.rpm
Build Date : Di 23 Jun 2026 13:04:04 CEST
ā¦
Source RPM : kscreen6-6.7.1-1.1.src.rpm
Build Date : Di 23 Jun 2026 12:55:15 CEST
ā¦
I observed then that the plasmashell and the crash handler (drkonqi6) crashed again on the first start.
I rebooted the system once more.
Now it seems that more program parts became usable for a while.
But I wonder still about information like the following if I try to check the current kscreen support.
Markus_Elfring@Sonne:~> systemsettings
org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
qrc:/kcm/kcm_landingpage/main.qml:278:21: Unable to assign [undefined] to QQuickItem*
vkDebug: Unable to open device : Datei oder Verzeichnis nicht gefunden (VK_ERROR_INCOMPATIBLE_DRIVER)
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
No suitable memory type found
QQuickWidget: failed to create depth/stencil buffer of size 938x793 and sample count 1
KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2
Speicherzugriffsfehler (Speicherabzug geschrieben) systemsettings
I can inspect display settings without such data processing surprises if I try the same program out from within an XFCE session (for example).
@elfring as indicated, those third party repositories and packages may not be helping. For example you have packman and VideoLan, itās either one or the otherā¦
Create a test user which will have a clean environment, login and test Plasma and applications.
Please show the output from inxi -GSaz to provide further information on your setup and hardware in use.
Markus_Elfring@Sonne:~> inxi -GSaz
System:
Kernel: 7.0.12-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/vmlinuz-7.0.12-1-default
root=/dev/mapper/bim-T--root splash=silent systemd.show_status=yes
resume=/dev/disk/by-uuid/b84c1e58-834e-4567-8ebf-e0ca6ad6dc5d
mitigations=auto quiet nosimplefb=1
Desktop: Xfce v: 4.20.2 tk: Gtk v: 3.24.52 wm: xfwm4 v: 4.20.0
with: xfce4-panel tools: avail: lxlock,xscreensaver vt: 2 dm: 1: GDM v: 50.1
2: LightDM v: 1.32.0 note: stopped 3: SDDM note: stopped Distro: openSUSE
Tumbleweed 20260625
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 730] vendor: ASUSTeK driver: nvidia
v: 470.256.02 alternate: nouveau,nvidia_drm non-free: series: 470.xx+
status: legacy-active (EOL~2024-09-xx) arch: Kepler-2 code: GKxxx
process: TSMC 28nm built: 2012-2018 pcie: gen: 2 speed: 5 GT/s lanes: 8
ports: active: none off: DVI-D-1 empty: HDMI-A-1,VGA-1 bus-ID: 04:00.0
chip-ID: 10de:1287 class-ID: 0300
Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.11
compositor: xfwm4 v: 4.20.0 driver: X: loaded: N/A
unloaded: modesetting,nouveau,vesa failed: nv,nvidia alternate: fbdev
gpu: nvidia,nvidia-nvswitch note: X driver n/a, try sudo/root
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 678x382mm (26.69x15.04")
s-diag: 778mm (30.64")
Monitor-1: DVI-D-0 res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 109
size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: kms_swrast surfaceless: drv: swrast x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 470.256.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GT 730/PCIe/SSE2
memory: 1.95 GiB
API: Vulkan v: 1.4.350 layers: 3 device: 0 type: discrete-gpu
name: NVIDIA GeForce GT 730 driver: nvidia v: 470.256.02
device-ID: 10de:1287 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 22.1.7 128 bits) driver: mesa llvmpipe v: 26.1.3 (LLVM 22.1.7)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,
kscreen-doctor, xfce4-display-settings gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
I am curious if corresponding software components can evolve into more desirable directions.
@elfring did you manually add nosimplefb=1 to the boot options? If so, on boot press the āeā key at the grub menu and remove the option at the end of the line starting ālinuxefiā and press F10 to continue booting and check that nvidia is loaded here;
Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.11
compositor: xfwm4 v: 4.20.0 driver: X: loaded: N/A <<================
unloaded: modesetting,nouveau,vesa failed: nv,nvidia alternate: fbdev
As you can see above itās āfailed: nv,nvidiaā
Such information might trigger further considerations.
The tool āNVIDIA X Server Settingsā does not present obvious open issues.
You occasionally provided further background information for corresponding clarification approaches.
@elfring unfortunately operating systems, applications, desktop environments, kernel etc move on, old forum threads and legacy hardware do notā¦
What was done then does not equate to what is needed now. I have a MacBook Pro that has dual graphics of the same kepler-2 architecture and works fine with the nouveau driver and Hyprland (peruse the screenshot sub forum).
Until the legacy driver is initiated and in use by the desktop environment, not a lot will be achieved.
Remember, users like myself are not in front of the hardware, so instead of bike sledding, I suggest you help yourself by responding with answers to the questions.
1 Like
I am also looking for solution approaches for hardware components which became ālegacyā somehow.
It is nice when they can occasionally work so long, isnāt it? 
A solution would be to do what you were asked for. Remove the kernel command line option and test.
1 Like
It was indicated that a kernel command line parameter like ānosimplefb=1ā had a desirable effect, wasnāt it?
Did you actually read what @malcolmlewis wrote?
Answering questions with unrelated questions is not a good way to solve technical issues. You should have already learnt that after so many years and so many MLās, projects, forums and others where you are permanently blocked for such unhelpful behaviour.
Here are still some ppl left which really try to help you. So stop arguing and try what experienced members like malcomlewis are asking you.
Writing your unrelated counter questions take more time then trying the proposed recommendations. Itās up to you.
5 Likes
Yes, of course.
It is an usual approach to achieve a better consensus.
There were occasionally special communication difficulties involved.
The relevance of selected information is evolving somehow.
I hope that we can benefit more from known software functionality.
I am one of those people that @hui means, that will not help you here anymore. Feel free to turn that as a quote into some pseudo philosophic debate course too, I am out.
1 Like
Do you see further clarification needs if you would also take another look at information from known issue trackers?
Do you see chances to influence software evolution in more desirable directions also according to known bug reports?
Do you see ways to steer your use of rhetorical questions in a more desirable direction, drawing on experiences from other communication channels where you were permanently ignored?
This is the openSUSE user forum. Not the Plasma developer channel. So what is your intention? If you belive you can substantially help the Plasma developers by adding usefull code, move to the correct communication channels and provide usefull patches.
4 Likes