Search Issue Tracker
Fixed
Fixed in 2021.3.16f1, 2022.2.2f1, 2023.1.0a20
Votes
19
Found in
2021.3.7f1
Issue ID
UUM-11724
Regression
No
[Linux] Editor crashes at "DisconnectGtkSignal(void*, GtkCallbackResponse (*)(), void*)" when opening floating windows
How to reproduce:
# Create and open a new project
# Open the Build setting window by going to the menu bar: File > Build Settings…
# Observe the crash
Reproducible with: 2021.3.6f1, 2021.3.7f1
Reproducible on: Ubuntu 22.04, Manjaro, Fedora, Pop OS, Linux Mint
Not reproducible on: Windows 10, Ubuntu, 20.04
Notes:
# Could not reproduce the issue on any testing machines with Nvidia GPUs and no user reports list these GPUs indicating that the crash may be related to AMD and Intel GPUs. Could be caused by the Mesa drivers
# The crash is triggered by opening the “Build Settings“, “Preferences“, “Project Settings“, “Package Manager“ and “Color Picker“ windows, opening the “Add Component“ dropdown, adding a script to a Game Object or when creating a new script in the Project panel. There may be other unlisted actions that trigger the crash
# The top 8 lines of the stack trace below occur in all instances of this issue
Crash stack trace:
{noformat}#0 0x0055dbb0f040dc in burst_signal_handler(int, siginfo_t*, void*)
#1 0x007f15b6fcbe60 in funlockfile
#2 0x007f15b75bc2fd in g_type_check_instance
#3 0x007f15b75b1e7c in g_signal_handlers_disconnect_matched
#4 0x0055dbb24e5843 in DisconnectGtkSignal(void*, GtkCallbackResponse (*)(), void*)
#5 0x0055dbb1d9019d in MenuItem::~MenuItem()
#6 0x0055dbb1d94833 in RemoveItemFromMenu(std::list<MenuItem, std::allocator<MenuItem> >*, core::basic_string_ref<char>)
#7 0x0055dbb1d94873 in RemoveItemFromMenu(std::list<MenuItem, std::allocator<MenuItem> >*, core::basic_string_ref<char>)
#8 0x0055dbb1d946b3 in MenuController::RemoveMenuItem(core::basic_string_ref<char>)
#9 0x0055dbb224ec86 in RecentScenesMenu::Build()
#10 0x0055dbb224ebee in RecentScenesMenu::Update()
#11 0x0055dbb1d909aa in MenuController::UpdateAllMenus(bool)
#12 0x0055dbb24cb5b7 in OnActivated(MenuItem*)
#13 0x007f15b7599349 in g_closure_invoke
#14 0x007f15b75acaef in g_signal_handler_disconnect
#15 0x007f15b75b395f in g_signal_emit_valist
#16 0x007f15b75b3ab3 in g_signal_emit
#17 0x007f15b7cc7f9c in gtk_widget_activate
#18 0x007f15b7b80a26 in gtk_menu_shell_activate_item
#19 0x007f15b7b80d03 in gtk_menu_shell_activate_item
#20 0x007f15b7d1f6b5 in gtk_window_position_get_type
#21 0x007f15b7599578 in g_closure_invoke
#22 0x007f15b75b2b8c in g_signal_emit_valist
#23 0x007f15b75b3ab3 in g_signal_emit
#24 0x007f15b7cc4fe4 in gtk_requisition_copy
#25 0x007f15b7b6a19f in gtk_lock_button_set_permission
#26 0x007f15b7b6bdac in gtk_main_do_event
#27 0x007f15b7836172 in gdk_drawing_context_is_valid
#28 0x007f15b786c3cf in gdk_x11_drag_context_get_type
#29 0x007f15b74a5291 in g_main_context_dispatch
#30 0x007f15b74a5538 in g_main_context_dispatch
#31 0x007f15b74a5853 in g_main_loop_run
#32 0x007f15b7b6ae85 in gtk_main
#33 0x0055dbb24e3d47 in main
#34 0x007f15b6dfcb80 in __libc_start_main
#35 0x0055dbb06ca029 in _start{noformat}
-
huantianad
Sep 01, 2022 23:32
I'm not sure if there's a quick fix, still getting this issue on NixOS for a while now.
-
xAdamQ
Sep 01, 2022 19:35
Did Anyone find a quick fix??
-
Mailson-M
Aug 31, 2022 16:28
Me too.
Got exactly the same issue on Linux Mint 21. -
shadoh
Aug 23, 2022 01:54
Hey guys I also had a ticket about this (which has now been marked duplicate), so thought I would share how I got it working.
Ok, so basically what I did was uninstall unityhub, it was previously installed via Pop Shop.
I then added the deb following the instructions for installing on ubuntu and installed it that way. Using apt from the unity repository.
docs.unity3d.com/hub/manual/InstallHub.html#install-hub-linuxI also had to install the SSH 1.1 package as well (otherwise I got a blank screen on Unity Hub).
forum.unity.com/threads/unity-hub-shows-a-black-screen.1287065/ (Bottom of the page)But after doing that it works, so there must’ve been a missing package or permission issue, weird.
-
Nitue
Aug 22, 2022 16:30
The ticket says "Could not reproduce the issue on any testing machines with Nvidia GPUs and no user reports list these GPUs". Don't know what are the testing GPUs, but this happens for me on with RTX 3080, driver version 515.48.07, PopOS! 22.04. Also tested on 510 driver.
Does not happen on Unity 2020 LTS.
-
ubuntu-user
Aug 22, 2022 10:19
this issue doesn't happens with 2020.3.38f1 version
Thanks all the Team
-
pacogarciaprofe
Aug 20, 2022 16:06
Same issue here!, tested on Fedora and KDE Neon
-
Jaycey
Aug 14, 2022 14:32
Got exactly the same issue on Linux Mint 21.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
- Crash on AMDUnityPlugin.DLL in specific built project when using FSR2 upscaler
- RenderObjects does not have any Depth texture bound when Event is set to AfterRenderingPostProcessing
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
Resolution Note (fix version 2023.1.0a20):
Fixed in 2023.1.0a20
Resolution Note (fix version 2022.2.2f1):
Fixed in 2022.2.2f1
Resolution Note (fix version 2021.3.16f1):
Fixed in 2021.3.16f1