Bug 1899803

Summary:	On first run each boot, takes a long time to run then shows error
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	krfb	Assignee:	Than Ngo <than>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	35	CC:	jreznik, kde-sig, rdieter, than
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	openqa
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-03 15:45:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Williamson 2020-11-20 04:23:19 UTC

On first run after each system boot, krfb takes a long time to start up - if run at a console, it pauses after the message "Initializing D-Bus connectivity with XDG Desktop Portal" - then shows an error dialog:

Error - Desktop Sharing

Failed to start the krfb server. Desktop sharing will not work. Try setting another port in the settings and restart krfb.

At the console, these errors appear:

Unsupported XDG Portal screencast interface version: 0
QObject::connect(FrameBuffer, RfbServerManager): invalid nullptr parameter

After hitting OK on this dialog, the main "Desktop Sharing" window appears. Subsequent runs of krfb before the next reboot go to this window immediately.

Comment 1 Ben Cotton 2021-02-09 16:12:07 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 2 Adam Williamson 2021-03-06 01:31:07 UTC

This still appears to be happening, more or less. openQA always hits it, and I can reproduce in a local VM when launching krfb through the menus. If I run it from a console, it seems to always start up immediately.

Comment 3 Adam Williamson 2021-06-25 17:22:20 UTC

Still happening on Rawhide too.

Comment 4 Ben Cotton 2021-08-10 13:39:59 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 5 Than Ngo 2022-05-03 15:45:21 UTC

this issue shuould be fixed in current 21.12.3-2