Skip to content

Troubleshooting Ubuntu Deployment Issue

Logs

VDI/SHD Session Logs

Description Path
Agent Logs /var/log/accops/dvm/agent.log

Domain Join Logs

Description Path
Hyprep Logs /var/log/accops/dvm/hyprep.log

Authentication Logs

Description Path
SSSD Logs /var/log/sssd/sssd.log

XRDP Logs

Description Path
XRDP /var/log/xrdp.log
XRDP-Sesman /var/log/xrdp-sesman.log

AUEM / CMDEXEC Logs

Description Path
Plugin Logs Directory /var/log/accops/plugins/
AUEM Log /var/log/accops/plugins/<username>/auem.log
CMDX Logs /var/log/accops/plugins/<username>/cmdexec.log

PAM Authentication Logs

OS Log File Path
Ubuntu /var/log/auth.log
RHEL /var/log/secure
General /var/log/messages

Important Files and Directories

  • Binaries and configuration files: /etc/accops/

  • Scripts: /etc/accops/dvm/scripts/

  • Logs: /var/log/accops/

Configurations and Other Troubleshooting

Google Chrome Keyring Authentication Issue

Description:

When launching Google Chrome in a Linux VDI/SHD session (Ubuntu 24), a Keyring Authentication Prompt appears requesting the administrator’s password. Since VDI/SHD users are typically non-admin users, they cannot proceed, causing disruptions to browser usage.

Root Cause:

  • Chrome tries to use the system keyring (gnome-keyring)

  • Non-admin users cannot unlock or access it

Workaround / Solution:

This issue can be resolved by forcing Chrome to use a basic password store instead of Keyring.

Steps to Fix:

  1. Open the Chrome launcher file:

    sudo nano /opt/google/chrome/google-chrome

  2. Locate the line:

    exec -a "$0" "$HERE/chrome" "$@"

  3. Modify it to:

    exec -a "$0" "$HERE/chrome" --password-store=basic "$@"

  4. Save and exit the file

Result:

  • Chrome will no longer prompt for keyring authentication.

  • Users can access Chrome normally.

Snapd Removal & Firefox (APT-Based Installation)

Description:

Firefox may fail to launch inside VDI/SHD sessions on Xubuntu because:

  • Default Firefox is installed via Snap.

  • Snap-based apps have compatibility issues with XRDP/Xorg sessions

Solution Overview

Remove snapd completely, then install Firefox using APT (native packages).

Steps to Fix:

  1. Remove snapd:

    sudo apt purge snapd -y

  2. Remove any existing snap Firefox:

    sudo rm -rf ~/snap

  3. Install Firefox using APT:

    sudo apt update

    sudo apt install firefox -y

Result:

  • Firefox launches successfully inside desktop sessions.

  • No XRDP/Snap compatibility issues

AD Domain Going Offline Frequently

Description:

Users may encounter the following error during login: User could not be authenticated. Please try again. [Error Code: LNA003]

Root Cause:

  • Domain controller resolution issues

  • Improper DNS or SSSD configuration

Solution 1: Update Domain Controllers in SSSD

  1. Open SSSD configuration file:

    sudo nano /etc/sssd/sssd.conf

  2. Add/update:

    ad_server = dc1.example.com, dc2.example.com

  3. Save the file

Solution 2: Fix DNS Search Domain

  1. Open file:

    sudo nano /etc/systemd/resolved.conf

  2. Check for:

    search

  3. Replace with:

    search example.com

  4. Restart service:

    sudo systemctl restart systemd-resolved

Alternate Solution 3: (If Solution 1 and 2 do not work)

Enable the flag below in sudo nano /etc/accops/dvm/agentconfig.json, then restart the service: sudo systemctl restart edcdvm.

Flag Name Default Value Possible Values Updated By Description
RestartsssdServiceIfDomainOffline false true / false System Restarts SSSD service
If the domain becomes offline.

Result:

  • Stable domain connectivity

  • Authentication issues resolved

Slow Application Launch on Ubuntu

Description:

While connecting and using Ubuntu 24, users may experience:

1) Black screen

2) Slow application launch

This is caused by snapd-desktop-integration issues with Xorg.

Solution:

  1. Open XRDP config:

    sudo nano /etc/xrdp/sesman.ini

  2. Set:

    ForcedAlternateShell=true

  3. Restart XRDP service:

    sudo systemctl restart xrdp

Result:

  • Improved session performance

  • Faster application launch

  • Eliminates black screen issues

Desktop Loading Screen (Black Screen Mitigation)

In case users experience a prolonged black screen when accessing their desktop sessions. To improve the user experience, a new loading UI has been introduced that displays session progress (such as authentication and desktop environment preparation), reducing perceived wait time.

Note

For the latest v4.0 releases, this configuration is enabled by default.

Configuration Steps: To enable the loading screen on the Linux VM:

  • Navigate to the configuration file:

    sudo nano /etc/xrdp/acc_login.ini

  • Enable the loading screen by setting:

    loading_screen_enabled=1

  • (Optional) To display the username on the loading screen, set:

    username_visible=1