After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778892 - GTK3 Apps crashing when started while connected via remote desktop
GTK3 Apps crashing when started while connected via remote desktop
Status: RESOLVED DUPLICATE of bug 777527
Product: gtk+
Classification: Platform
Component: Backend: Win32
3.22.x
Other Windows
: Normal critical
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-02-18 21:47 UTC by Johannes Schriewer
Modified: 2017-02-19 14:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Johannes Schriewer 2017-02-18 21:47:39 UTC
It seems something in the GDK initialization process is wrong.

If I run gtk3-demo.exe from my local workstation everything is working perfectly, if I run it while connected via Remote Desktop the apps crash.

It reminds me somehow of bug #774379 (https://bugzilla.gnome.org/show_bug.cgi?id=774379) where something similar happened when a graphics tablet was connected.

I tried different color depths on the RDP connection but it does not change anything. What I observed is that there is a "Remote Desktop Mouse"-Device in the Device manager (HID subsection) when connected via RDP. It is not there if the RDP connection is not running.

I have a 3D-Connexion space mouse connected if that matters somehow (the driver has an emulation device that will not vanish if I unplug the thing, but it does not change the crashing behaviour either if it's plugged in or not).

If the GTK3 app is started locally and I connect to the workstation by RDP afterwards it does not go down but works as expected, it has to be something in the initialization.
Comment 1 Daniel Boles 2017-02-18 21:53:25 UTC
Please post a backtrace of the crash. There's not much anyone can do without that.
Comment 2 LRN 2017-02-19 07:28:04 UTC
Which version of GTK are you using? Is it 3.22.8? Because it has bug 777527 fixed, which might be related.
Comment 3 Johannes Schriewer 2017-02-19 14:52:08 UTC
Ok just upgraded to 3.22.8, seems to work there. So the cause seems to be the same as bug 777527.

*** This bug has been marked as a duplicate of bug 777527 ***