** No longer affects: gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/2062949

Title:
  gnome-remote-desktop-daemon crashed with SIGSEGV in
  g_main_context_iteration()

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  In 24.04, attempting to launch into a Remote Login RDP session (which
  uses the wayland compositor) with an Nvidia GPU connected on the host
  gives a black screen. The purpose of having the GPU is to provide HW
  acceleration to gnome-remote-desktop on the host (the RDP host is a
  24.04 VM.) The Nvidia GPU does not have a display adapter, therefore a
  dummy adapter cannot be used to fool the machine into believing there
  is a monitor attached. The Remote Login session is only black screen
  if the Nvidia GPU is attached. When the RDP client (I am using the
  standard Remote Desktop connection client on a Windows 10 device) logs
  out from gnome-remote-desktop, both grd and gnome-shell crash with
  SIGSEGV.

  In Ubuntu version 22.04, attaching a Nvidia GPU to the 22.04 host VM
  and launching a gnome-remote-desktop on "Ubuntu on Wayland" did not
  cause a crash or any black screens, and the RDP instance had fully
  supported HW acceleration for the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-remote-desktop 46.1-1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Apr 19 00:29:37 2024
  ExecutablePath: /usr/libexec/gnome-remote-desktop-daemon
  InstallationDate: Installed on 2024-04-18 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  ProcCmdline: /usr/libexec/gnome-remote-desktop-daemon --system
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x76f9b13c9a11:        cmpq   $0x0,0x18(%rax)
   PC (0x76f9b13c9a11) ok
   source "$0x0" ok
   destination "0x18(%rax)" (0x00000018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-remote-desktop
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-remote-desktop-daemon crashed with SIGSEGV in 
g_main_context_iteration()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2062949/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to