How to start the xdg-desktop-portal service?

Jetson Orin Nano
Ubuntu 22.04
Rel. 5.15.136-tegra
L4T 36.3.0

The JON is attached via a HDMI-Switch to the monitor.

When I boot the JON with the monitor running, I have video output.

When I boot the JON via Putty and switch to the monitor, I have no signal.

The difference is that xdg-desktop-portal is loaded or not.

Switching the GUI off with “INIT 3” the xdg-desktop-portal.service stopped, but switching the GUI on “INIT 5” again only xorg and Gnome-shell are reloaded - NOT xdg-desktop-portal.service.

When I try to start the service in Putty it is always

-bash: xdg-desktop-portal: command not found

I tried now a lot of command and name variations (even asked AI), but to no avail.

Question: How to I start the service or get video output going via PUTTY without reboot?

Thank you for your suggestions
Olaf

Hi tech120,

Are you using the devkit or custom board for Orin Nano?

How did you start the service?

Please share the result of the following command on your board.

$ systemctl status xdg-desktop-portal.service

Jtop says that it is a 0003 board.

The services starts on boot.

Unit xdg-desktop-portal.service could not be found.

Sorry that do you mean the SKU 0003?
Please share the result of the following command on your board.

$ cat /etc/nv_tegra_relesae
$ cat /etc/nv_boot_control.conf

Please run the following command instead.

$ systemctl --user status xdg-desktop-portal.service

jetson@jetson:/etc$ cat /etc/nv_tegra_release

R36 (release), REVISION: 3.0, GCID: 36191598, BOARD: generic, EABI: aarch64, DATE: Mon May 6 17:34:21 UTC 2024

KERNEL_VARIANT: oot

TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia

jetson@jetson:/etc$ cat /etc/nv_boot_control.conf
TNSPEC 3767-300-0003-M.2-1-1-jetson-orin-nano-devkit-
COMPATIBLE_SPEC 3767–0003–1–jetson-orin-nano-devkit-
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

etson@jetson:/etc$ systemctl --user status xdg-desktop-portal.service
● xdg-desktop-portal.service - Portal service
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static)
Active: active (running) since Thu 1970-01-01 01:00:41 CET; 54 years 7 mon>
Main PID: 2529 (xdg-desktop-por)
Tasks: 6 (limit: 8815)
Memory: 5.4M
CPU: 256ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/xdg-de>
└─2529 /usr/libexec/xdg-desktop-portal

Jan 01 01:00:39 jetson systemd[1553]: Starting Portal service…
Jan 01 01:00:41 jetson systemd[1553]: Started Portal service.
lines 1-12/12 (END)…skipping…
● xdg-desktop-portal.service - Portal service
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static)
Active: active (running) since Thu 1970-01-01 01:00:41 CET; 54 years 7 mon>
Main PID: 2529 (xdg-desktop-por)
Tasks: 6 (limit: 8815)
Memory: 5.4M
CPU: 256ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/xdg-de>
└─2529 /usr/libexec/xdg-desktop-portal

Jan 01 01:00:39 jetson systemd[1553]: Starting Portal service…
Jan 01 01:00:41 jetson systemd[1553]: Started Portal service.

systemctl status xdg-desktop-portal.service


xdg-desktop-portal loads now again, but when I switch the monitor to Jetson direct input there is still no signal.

systemctl status.txt (25.1 KB)

I’m not clear about this.
Could you share the detailed steps how you did to reproduce the issue?

Is there any error showing in dmesg or /var/log/Xorg.0.log?

Do you identifiy this as a devkit (what I ordered) but should be, according to specs, a SKU 0005
or as a custom board?

Set-up:
Jetson Orin Nano connected by cable to a HDMI switch on port 2, which connects to the monitor.

A Windows 11 laptop which connects via the same HDMI switch to port 1.

Scenario 1:
HDMI switch is on port 2.
Boot the Jetson, you see the process and the logos on screen. The green desktop appears.
When you switch between the two ports, there is always a video signal on port 2.
From the laptop you can operate the Jetson via Putty without problem.

Scenario 2:
HDMI switch is on port 1.
Boot the Jetson. Switch to port 2. The monitor is black and has no video signal.
When you switch between the two ports, there is never a video signal on port 2.
From the laptop you can operate the Jetson via Putty without problem.

1 Like

dmesg with video.txt (5.0 KB)
dmesg without video.txt (5.0 KB)
Where it says “Machine model: Orin Nano 8GB for DSBOARD-ORNX-LAN”, that is not correct.
I could not get the SDKManager to work, but with a helper script, which contains this text, the update worked.

Xorg.0.log with video.txt (3.9 KB)
Xorg.0.log without video.txt (3.9 KB)

The Xorg.0.log without video starts at number15.820, while
the Xorg.0.log with video starts at number18.081
Q: Is there something missing in the load?

Where did you buy this board? Could you take a photo on your board?

Have you also tried DP connector? Or the issue is specific to HDMI?

It seems you are using the custom carrier board from Forecr?

How did you flash the board before?

  1. It is from Yahboom and sold as a Jetson Orin Nano Developer Kit.
    It has an SDD and a WiFi Card, but comes without SD-card drive.

  2. I bought this on Amazon Germany in the Yahboom shop.
    (NVidia is neither selling in nor shipping to Switzerland).

  3. The cable is a converter: Display Port to HDMI. On the board is a display port.

  4. No, it is not a Forecr. I used one of their scripts to prepare the installation files on the host, to update the target.

It looks so like the devkit but there’re black on 40-pins expansion header rather than green on your board.
I’m not quite sure if our official BSP package can work well on this board.

Sorry that what do you mean about port 1/port 2 here? (do you mean the HDMI port of your monitor?)
Could you share the block diagram of your conenctions?

Do you have another monitor to reproduce the same issue to clarify if the issue is specific to the current monitor?

Not at the moment. Give me three weeks and I am able to run the test.

Okay, please let us know the result once you have the setup to clarify the issue.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.