Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pairing notification does nothing #3585

Open
2 tasks done
abrandst opened this issue Jan 23, 2025 · 3 comments
Open
2 tasks done

Pairing notification does nothing #3585

abrandst opened this issue Jan 23, 2025 · 3 comments

Comments

@abrandst
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your issue described in the documentation?

  • I have read the documentation

Is your issue present in the latest beta/pre-release?

This issue is present in the latest pre-release

Describe the Bug

On Fedora 41 with a KDE session running sunshine, pair a client. A notification appears:
"Incoming Pairing Request Click here to complete the pairing process"

Clicking that notification does nothing.

The same behavior is present in both X11 and Wayland KDE sessions. Sunshine was installed from flatpack.

Expected Behavior

Clicking that notification pairs the client or opens some dialog to pair the client.

Additional Context

No response

Host Operating System

Linux

Operating System Version

Fedora Core 41

Architecture

amd64/x86_64

Sunshine commit or version

v2025.122.141614

Package

Linux - flathub/flatpak

GPU Type

NVIDIA

GPU Model

RTX 3060

GPU Driver/Mesa Version

565.77

Capture Method

None

Config

default config with no adaptions

Apps

Relevant log output

no output relating to the request
@ReenigneArcher
Copy link
Member

Clicking that notification pairs the client or opens some dialog to pair the client.

It is supposed to open the web ui. Does the open sunshine option work from the tray icon?

Please restart Sunshine, and try to do a pair again. Then share the full logs.

@abrandst
Copy link
Author

Rebooted, and restarted sunshine. The Web UI opens normally from the task bar. The logs below are all from before the pairing - the pairing request does not generate any log entry, nor does it show up in the web ui itself.

[2025-01-23 16:29:31.372]: Info: Sunshine version: v2025.122.141614
[2025-01-23 16:29:31.372]: Info: Package Publisher: LizardByte
[2025-01-23 16:29:31.372]: Info: Publisher Website: https://app.lizardbyte.dev
[2025-01-23 16:29:31.372]: Info: Get support: https://app.lizardbyte.dev/support
[2025-01-23 16:29:31.414]: Info: System tray created
[2025-01-23 16:29:31.844]: Info: Found [1] outputs
[2025-01-23 16:29:31.844]: Info: Virtual Desktop: 3840x2160
[2025-01-23 16:29:31.844]: Info: XrandR: available
[2025-01-23 16:29:31.844]: Info: -- Output --
[2025-01-23 16:29:31.844]: Info: Resolution: 3840x2160
[2025-01-23 16:29:31.844]: Info: Offset: 0x0
[2025-01-23 16:29:31.883]: Error: Couldn't release NvFBC context from current thread:
[2025-01-23 16:29:31.883]: Info: Detecting displays
[2025-01-23 16:29:31.898]: Info: Detected display: HDMI-0 (id: 0)HDMI-0 connected: false
[2025-01-23 16:29:31.898]: Info: Detected display: DP-0 (id: 1)DP-0 connected: true
[2025-01-23 16:29:31.898]: Info: Detected display: DP-1 (id: 2)DP-1 connected: false
[2025-01-23 16:29:31.898]: Info: Detected display: DP-2 (id: 3)DP-2 connected: false
[2025-01-23 16:29:31.899]: Info: Detected display: DP-3 (id: 4)DP-3 connected: false
[2025-01-23 16:29:31.899]: Info: Detected display: DP-4 (id: 5)DP-4 connected: false
[2025-01-23 16:29:31.899]: Info: Detected display: DP-5 (id: 6)DP-5 connected: false
[2025-01-23 16:29:31.899]: Info: Detected display: HDMI-1-1 (id: 7)HDMI-1-1 connected: false
[2025-01-23 16:29:31.899]: Info: Detected display: DP-1-1 (id: 8)DP-1-1 connected: false
[2025-01-23 16:29:31.982]: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. //
[2025-01-23 16:29:31.982]: Info: Trying encoder [nvenc]
[2025-01-23 16:29:31.982]: Info: Screencasting with NvFBC
[2025-01-23 16:29:32.147]: Info: Creating encoder [h264_nvenc]
[2025-01-23 16:29:32.147]: Info: Color coding: SDR (Rec. 601)
[2025-01-23 16:29:32.147]: Info: Color depth: 8-bit
[2025-01-23 16:29:32.147]: Info: Color range: JPEG
[2025-01-23 16:29:32.526]: Info: Creating encoder [hevc_nvenc]
[2025-01-23 16:29:32.526]: Info: Color coding: SDR (Rec. 601)
[2025-01-23 16:29:32.526]: Info: Color depth: 8-bit
[2025-01-23 16:29:32.526]: Info: Color range: JPEG
[2025-01-23 16:29:32.791]: Info: Creating encoder [av1_nvenc]
[2025-01-23 16:29:32.791]: Info: Color coding: SDR (Rec. 601)
[2025-01-23 16:29:32.791]: Info: Color depth: 8-bit
[2025-01-23 16:29:32.791]: Info: Color range: JPEG
[2025-01-23 16:29:32.799]: Warning: [av1_nvenc @ 0x563a92160a00] Codec not supported
[2025-01-23 16:29:32.800]: Error: [av1_nvenc @ 0x563a92160a00] Provided device doesn't support required NVENC features
[2025-01-23 16:29:33.051]: Error: Could not open codec [av1_nvenc]: Function not implemented
[2025-01-23 16:29:33.082]: Error: Couldn't release NvFBC context from current thread:
[2025-01-23 16:29:33.082]: Info: Screencasting with NvFBC
[2025-01-23 16:29:33.206]: Info: Creating encoder [hevc_nvenc]
[2025-01-23 16:29:33.206]: Info: Color coding: SDR (Rec. 709)
[2025-01-23 16:29:33.206]: Info: Color depth: 10-bit
[2025-01-23 16:29:33.206]: Info: Color range: JPEG
[2025-01-23 16:29:33.228]: Error: cuda::cuda_t doesn't support any format other than AV_PIX_FMT_NV12
[2025-01-23 16:29:33.502]: Error: Couldn't release NvFBC context from current thread:
[2025-01-23 16:29:33.502]: Info:
[2025-01-23 16:29:33.502]: Info: // Ignore any errors mentioned above, they are not relevant. //
[2025-01-23 16:29:33.502]: Info:
[2025-01-23 16:29:33.502]: Info: Found H.264 encoder: h264_nvenc [nvenc]
[2025-01-23 16:29:33.502]: Info: Found HEVC encoder: hevc_nvenc [nvenc]
[2025-01-23 16:29:33.504]: Info: Configuration UI available at [https://localhost:47990]
[2025-01-23 16:29:33.504]: Info: Adding avahi service fedora
[2025-01-23 16:29:34.483]: Info: Avahi service fedora successfully established.

@ReenigneArcher
Copy link
Member

No idea, they're almost the same exact code.

void launch_ui() {
std::string url = "https://localhost:" + std::to_string(net::map_port(confighttp::PORT_HTTPS));
platf::open_url(url);
}
void launch_ui_with_path(std::string path) {
std::string url = "https://localhost:" + std::to_string(net::map_port(confighttp::PORT_HTTPS)) + path;
platf::open_url(url);
}

It's called from:

tray.notification_cb = []() {
launch_ui_with_path("/pin");
};

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants