Bug 2431541

Summary:	Enable crash-reporting dialog for KDE Installer (Anaconda)
Product:	[Fedora] Fedora	Reporter:	Petr Sklenar <psklenar>
Component:	anaconda-webui	Assignee:	Katerina Koukiou <kkoukiou>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	alpha, kde-sig, kkoukiou, kparal, mkolman, ngompa13, nicolas.fella, rvykydal
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-webui-65-1.fc44 anaconda-webui-65-1.fc45	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-02-13 19:18:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Sklenar 2026-01-21 10:10:34 UTC

When testing Anaconda in KDE, debugging is currently difficult.
The QA team would like to test how the installer behaves during a crash.

On the Fedora Workstation (Gnome) anaconda WebUI (as its firefox), testers can use F12 to send a snippet:
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla#How_to_test_on_Anaconda_WebUI

which triggers a bug-reporting dialog for the Anaconda product.
----
We are looking for a similar way to trigger this debug/reporting flow in KDE installer environment and installer is running by slitherer.

Reproducible: Always

Steps to Reproduce:
1. have a KDE installer image
2. launch the installer
???? trigger/access debug mode or the crash-reporting dialog.
Actual Results:
no way to debug anaconda, in KDE environment

Expected Results:
trigger/access debug mode or the crash-reporting dialog.

Comment 1 Neal Gompa 2026-01-28 09:31:26 UTC

Slitherer needs to be launched with a setting for a debugging port. More details of how to access to QtWebEngine JS console are documented here: https://doc.qt.io/qt-6/qtwebengine-debugging.html

Comment 2 Neal Gompa 2026-01-28 09:31:52 UTC

Most likely you'd want to use the environment variable to make it work.

Comment 3 Kamil Páral 2026-02-03 15:09:04 UTC

Reassigning to Anaconda so that they can make necessary changes so that QA can test the crash reporting dialog in KDE.

Comment 4 Katerina Koukiou 2026-02-06 12:33:31 UTC

Added a way to trigger the crash report dialog: https://github.com/rhinstaller/anaconda/pull/6888#pullrequestreview-3762822369

Comment 5 Katerina Koukiou 2026-02-06 12:34:11 UTC

Sorry incorrect paste: I meant this: https://github.com/rhinstaller/anaconda-webui/pull/1162

Comment 6 Kamil Páral 2026-02-06 12:49:35 UTC

Awesome, Katerina! Is this just for KDE, or any environment with Anaconda WebUI (that would be ideal)?

Comment 7 Fedora Update System 2026-02-13 12:01:56 UTC

FEDORA-2026-e883c84e3e (anaconda-44.20-1.fc45 and anaconda-webui-65-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-e883c84e3e

Comment 8 Fedora Update System 2026-02-13 12:06:55 UTC

FEDORA-2026-db94b09323 (anaconda-44.20-1.fc44 and anaconda-webui-65-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-db94b09323

Comment 9 Fedora Update System 2026-02-13 19:18:46 UTC

FEDORA-2026-db94b09323 (anaconda-44.20-1.fc44 and anaconda-webui-65-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2026-02-13 19:45:45 UTC

FEDORA-2026-e883c84e3e (anaconda-44.20-1.fc45 and anaconda-webui-65-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.