Maximizing nautilus freezes gnome.

Shino · 2024-10-31 16:25:17

Hi,

since one of the latest updates, I experience the issue that maximizing nautilus freezes my entire desktop environment.
During the animation of the window maximizing, everything freezes and gnome is not responsive anymore. I'm sometimes able to switch to another tty, log in, and kill nautilus. Gnome becomes responsive after that again.
As far as I can see, this issue is only present when using "Gnome on Xorg" (selected in GDM at login). Wayland seems to work.

However, I'm unable to use wayland, because lots oof things aren't working properly under wayland. For instance, the dropdown menues in FreeCAD do not work when using gnome natively on Wayland.

Does anyone else experience that issue?
As far as I could tell, nautilus is the only application, that behaves this way.

I use the integrated graphics of my i7-6700K processor

FYI: program versions of gnome mutter and the xorg stuff.
Please let me know if you need anything else.

gnome-app-list 1.0-1
gnome-autoar 0.4.5-1
gnome-bluetooth-3.0 47.1-1
gnome-color-manager 3.36.0+r62+g82000f1d-1
gnome-common 3.18.0-5
gnome-console 47.1-1
gnome-contacts 47.0-1
gnome-control-center 47.1.1-1
gnome-desktop 1:44.1-1
gnome-desktop-4 1:44.1-1
gnome-desktop-common 1:44.1-1
gnome-keyring 1:46.2-1
gnome-logs 45.0-1
gnome-session 47.0.1-1
gnome-settings-daemon 47.1-1
gnome-shell 1:47.1-1
gnome-shell-extensions 47.1-1
libnautilus-extension 47.0-3
mutter 47.1-1
nautilus 47.0-3
xdg-desktop-portal-gnome 47.1-1
xorg-fonts-encodings 1.1.0-1
xorg-mkfontscale 1.2.3-1
xorg-server 21.1.13-1
xorg-server-common 21.1.13-1
xorg-setxkbmap 1.3.4-2
xorg-xauth 1.1.3-1
xorg-xhost 1.0.9-2
xorg-xinit 1.4.2-2
xorg-xinput 1.6.4-2
xorg-xkbcomp 1.4.7-1
xorg-xmodmap 1.0.11-2
xorg-xprop 1.2.7-1
xorg-xrandr 1.5.2-2
xorg-xrdb 1.2.2-2
xorg-xset 1.2.5-2
xorg-xsetroot 1.1.3-2
xorg-xwayland 24.1.3-1

Last edited by Shino (2024-10-31 16:27:51)

seth · 2024-10-31 18:28:43

Do you get the same w/ a fresh user account?

As far as I could tell, nautilus is the only application, that behaves this way.

What's the output of "xprop" on the (unmaximized) window?

Shino · 2024-10-31 22:07:44

Same happens with a fresh user. This is how it looks:
Screenshot of broken nautilus

seth wrote:

What's the output of "xprop" on the (unmaximized) window?

_NET_WM_OPAQUE_REGION(CARDINAL) = 73, 55, 1289, 560
_GTK_FRAME_EXTENTS(CARDINAL) = 61, 61, 55, 67
_GTK_THEME_VARIANT(UTF8_STRING) = "dark"
WM_STATE(WM_STATE):
		window state: Normal
		icon window: 0x0
_NET_WM_DESKTOP(CARDINAL) = 0
_GTK_EDGE_CONSTRAINTS(CARDINAL) = 170
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW
_NET_WM_STATE(ATOM) = 
WM_HINTS(WM_HINTS):
		Client accepts input or input focus: True
		Initial state is Normal State.
		bitmap id # to use for icon: 0x3e00008
		bitmap id # of mask for icon: 0x3e00017
		window id # of group leader: 0x3e00002
_NET_WM_ICON(CARDINAL) = 	Icon (48 x 48):
	*** REMOVED ICON ***


_GTK_WINDOW_OBJECT_PATH(UTF8_STRING) = "/org/gnome/Nautilus/window/1"
_GTK_APPLICATION_OBJECT_PATH(UTF8_STRING) = "/org/gnome/Nautilus"
_GTK_UNIQUE_BUS_NAME(UTF8_STRING) = ":1.355"
_GTK_APPLICATION_ID(UTF8_STRING) = "org.gnome.Nautilus"
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x1, 0x0, 0x0, 0x0
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
XdndAware(ATOM) = BITMAP
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 65011718, 65011719
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x3e00005
WM_CLIENT_LEADER(WINDOW): window id # 0x3e00002
_NET_WM_PID(CARDINAL) = 33044
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "okabe"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		program specified minimum size: 482 by 502
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST
WM_CLASS(STRING) = "org.gnome.Nautilus", "org.gnome.Nautilus"
WM_ICON_NAME(STRING) = "Home"
_NET_WM_ICON_NAME(UTF8_STRING) = "Home"
WM_NAME(STRING) = "Home"
_NET_WM_NAME(UTF8_STRING) = "Home"

Last edited by Shino (2024-10-31 22:25:30)

Gusfit · 2024-10-31 22:55:44

Same exact issue here, Been troubleshooting for the last hour now. I've even reinstalled gnome and the issue persists. Also on X11, Gnome 47

icar · 2024-10-31 23:46:16

Can you try Wayland and launching freecad with QT_QPA_PLATFORM=wayland ?

seth · 2024-11-01 07:53:11

The OP wrote:

using "Gnome on Xorg" (selected in GDM at login). Wayland seems to work.

Nautilus also isn't a Qt client?

Nautilus doesn't enforce a certain geometry so no conflict potential there.
This looks like an unredirection problem.
1. does it "fix" when you unmaximize nautilus?
2. are other (gtk4/libadwaita) clients affected when you fullscreen them?
3. if we completely ignore nautilus and just go with the symptoms: do you have xf86-video-intel installed (in general please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General )

There seems to be an extension to disable fullscreen unredirection, https://wiki.archlinux.org/title/GNOME/ … D_Graphics
But we'll postpone that route until we've more data

Shino · 2024-11-01 10:07:59

icar wrote:

Can you try Wayland and launching freecad with QT_QPA_PLATFORM=wayland ?

Does not help with freecad. Usually whenever an update sneaks in Wayland as default I tend to realize it within a few hours because a lot of stuff isn't working. Dropdown / contexxt menues. Screenshares in chromium etc.

seth wrote:

1. does it "fix" when you unmaximize nautilus?

The unmaximizing animation does not freeze. However, after maximizing a nautius window the session is toast until I kill nautilus. So to get a maximized nautilus window, I need to maximize it, go to tty, kill nautilus, and then start nautilus again and it opens maximized.

seth wrote:

are other (gtk4/libadwaita) clients affected when you fullscreen them?

Not that I can tell. gedit (which seems to be gtk4 now) works, Evolution works. My own GTK applications work.

seth wrote:

do you have xf86-video-intel installed

No. I removed it some time ago as suggested in this topic: https://bbs.archlinux.org/viewtopic.php?id=291530

Shino · 2024-11-01 10:15:51

So for all interested. I figured out a solution. Besides my integrated intel graphics, I had an nvidia RTX A2000 installed, which I used for some Cuda computations. I haven't used it for graphics.
Removing this nvidia card solves the issue.

seth · 2024-11-01 12:52:36

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General (w/ the nvidia GPU in place)

Gusfit · 2024-11-01 15:48:54

I never tried QT_QPA_PLATFORM=wayland but everything else is the same on my end as in Shino's last reply. Running EndeavourOS installed just a few days ago (Lenovo Yoga 720 15IKB w/i7-7700HQ + GTX1050). Up to date mesa drivers. Wayland has no issues, smooth transitions. In comparing the two I did notice that in X11 the minimize transition has a small amount of stutter.

I only switched to X11 in the first place because it seemed like wayland might had some incompatibilities with extensions, and the cursor was enlarged over certain windows. Switching back it seems like everything is working properly so I might just stick with it. But it would be nice to understand what happeneed, when X11 was working fine up until then - quick, responsive.

Here's my x11 xorg log - https://pastebin.com/QJxcp3AC

and journalctl - https://pastebin.com/DuHDwypj

Seems to be related to "Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message" on lines 49 and 181 in journalctl.

seth · 2024-11-01 16:15:16

But those are

Nov 01 08:27:33 user-80x7 gnome-shell[1403]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2000004 (Loading…)
Nov 01 08:27:55 user-80x7 gnome-shell[1403]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800004 (Console)

console and "whatever", not so much nautilus.

Can you disable the nvidia GPU and does that have the same consequnces as #8 ?
(You're running X11 via the modesetting driver on the intel chip in regular prime mode. No outputs attached ot the nvidia chip)

Shino · 2024-11-01 18:10:54

seth wrote:

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General (w/ the nvidia GPU in place)

Here it is
https://pastebin.com/87Y5rQbt

seth · 2024-11-01 18:59:12

[     5.416] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 12 14:37:20 2024

The log is very dated, but otherwise matches Gusfit's (unsupicious) setup.
Sure that disabling/removing the nvidia chip didn't just propell you into the (default) wayland?

Does the issue manifest if you disable the second output?

Shino · 2024-11-01 19:05:25

seth wrote:

[     5.416] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 12 14:37:20 2024
The log is very dated, but otherwise matches Gusfit's (unsupicious) setup.
Sure that disabling/removing the nvidia chip didn't just propell you into the (default) wayland?
Does the issue manifest if you disable the second output?

Sorry about the old log. I haven't checked the date. There is no newer one available in /var/log.
Disabling the second output does not change anything.

I've attached the output of the journal here: https://pastebin.com/sHu2ULpE

Last edited by Shino (2024-11-01 19:16:12)

Gusfit · 2024-11-01 19:20:56

I swapped from switchable graphics to uma in the bios and confirmed it was disabled with lspci. Same result as Shino, windows are now able to maximize no problem. Still has some lag compared with Wayland, now I'm starting to question if that was there before...

Maybe a driver reinstall is in order?

seth · 2024-11-01 19:28:25

I doubt that reinstalling an driver will achieve anything - the X11 server doesn't run on the nvidia GPU, it should™ not even be used.
I could imagine sth. like https://wiki.archlinux.org/title/PRIME# … ronization getting into the way, but
1. all involved outputs are on the same GPU
2. why only nautilus

Can you run eg. an openbox session w/ and w/o picom and try to maxmize nautilus there?
Also what if you start gnome manually, w/o GDM?
Does GDM still run on wayland for either of you?

tekstryder · 2024-11-01 19:28:37

Shino wrote:

So for all interested. I figured out a solution. Besides my integrated intel graphics, I had an nvidia RTX A2000 installed, which I used for some Cuda computations. I haven't used it for graphics.
Removing this nvidia card solves the issue.

Ha, I almost asked yesterday if you had nVidia you didn't realize.

You've hit:

https://gitlab.gnome.org/GNOME/gtk/-/issues/7035

seth · 2024-11-01 19:48:15

gdk_vulkan_context_surface_resized

They're not even running on the nvidia chip…

killall nautilus
GSK_RENDERER=gl nautilus

still a problem?

Does

killall nautilus
MESA_VK_DEVICE_SELECT='8086:1912!' MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 nautilus # Shino
MESA_VK_DEVICE_SELECT='8086:591b!' MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 nautilus # Gusfit

work?

Shino · 2024-11-01 20:29:42

seth wrote:

gdk_vulkan_context_surface_resized

They're not even running on the nvidia chip…

killall nautilus
GSK_RENDERER=gl nautilus

still a problem?

Does

killall nautilus
MESA_VK_DEVICE_SELECT='8086:1912!' MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 nautilus # Shino
MESA_VK_DEVICE_SELECT='8086:591b!' MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 nautilus # Gusfit

work?

1) GSK_RENDERER.... -> Does not work. Same problem
2) MESA_VK_DEVICE_SELECT='8086:1912!' MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 nautilus -> Does not work. Same problem.

seth · 2024-11-01 20:35:21

I really wonder what nutilus is doing on the nvidia GPU there, can you attach gdb to the stalled process and confirm it's looping in the nvidia driver?

tekstryder · 2024-11-01 20:45:27

Shino wrote:

1) GSK_RENDERER....

While ensuring an X11 session, please post the output of

GSK_DEBUG=renderer nautilus

Gusfit · 2024-11-01 20:51:32

-I ran xrandr --prop and the output was identical, switchable graphics compared with uma. Nothing in there referring to prime synchronization.

-Changing GSK_RENDERER and MESA_VK_DEVICE_SELECT end up with about the same result - a frozen laggy nautilus.

-Wayland seems to work great.

Side note - when switchable graphics are enabled lspci reports

00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05)

and

01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1)

I'll try out openbox in a bit. Oh and thanks for the link to that issue tekstryder

Shino · 2024-11-01 20:52:18

seth wrote:

I really wonder what nutilus is doing on the nvidia GPU there, can you attach gdb to the stalled process and confirm it's looping in the nvidia driver?

Yep. Some threads are in the nvidia stuff.

Thread 1 "nautilus" received signal SIGINT, Interrupt.
0x00007643bbdd663d in poll () from /usr/lib/libc.so.6
(gdb) thread apply all where

Thread 16 (Thread 0x7643afe006c0 (LWP 9987) "pool-org.gnome."):
#0  0x00007643bbde21fd in syscall () from /usr/lib/libc.so.6
#1  0x00007643bd22dc37 in g_cond_wait_until () from /usr/lib/libglib-2.0.so.0
#2  0x00007643bd1c3955 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x00007643bd1c3ac8 in g_async_queue_timeout_pop () from /usr/lib/libglib-2.0.so.0
#4  0x00007643bd233a30 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0x00007643bd22f026 in ?? () from /usr/lib/libglib-2.0.so.0
#6  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#7  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 14 (Thread 0x7643b74006c0 (LWP 9674) "pool-spawner"):
#0  0x00007643bbde21fd in syscall () from /usr/lib/libc.so.6
#1  0x00007643bd22cf20 in g_cond_wait () from /usr/lib/libglib-2.0.so.0
#2  0x00007643bd1c398c in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x00007643bd233137 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x00007643bd22f026 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7643b6a006c0 (LWP 9675) "gmain"):
#0  0x00007643bbdd6bb0 in ppoll () from /usr/lib/libc.so.6
#1  0x00007643bd25e227 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007643bd1faa55 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007643bd1faab2 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x00007643bd22f026 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7643b60006c0 (LWP 9676) "gdbus"):
#0  0x00007643bbdd6bb0 in ppoll () from /usr/lib/libc.so.6
#1  0x00007643bd25e227 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007643bd1fc287 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#3  0x00007643bc40dbc4 in ?? () from /usr/lib/libgio-2.0.so.0
#4  0x00007643bd22f026 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6
--Type <RET> for more, q to quit, c to continue without paging--

Thread 11 (Thread 0x7643b56006c0 (LWP 9678) "pool-org.gnome."):
#0  0x00007643bbde21fd in syscall () from /usr/lib/libc.so.6
#1  0x00007643bd22cf20 in g_cond_wait () from /usr/lib/libglib-2.0.so.0
#2  0x00007643bd1c398c in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x00007643bd233a90 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x00007643bd22f026 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 10 (Thread 0x7643acc006c0 (LWP 9684) "nautilus"):
#0  0x00007643bbde21fd in syscall () from /usr/lib/libc.so.6
#1  0x00007643bd22cf20 in g_cond_wait () from /usr/lib/libglib-2.0.so.0
#2  0x00007643bd1c398c in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x00007643bd1c39fd in g_async_queue_pop () from /usr/lib/libglib-2.0.so.0
#4  0x00007643bb7395fc in ?? () from /usr/lib/libpangoft2-1.0.so.0
#5  0x00007643bd22f026 in ?? () from /usr/lib/libglib-2.0.so.0
#6  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#7  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7643a3e006c0 (LWP 9686) "dconf worker"):
#0  0x00007643bbdd6bb0 in ppoll () from /usr/lib/libc.so.6
#1  0x00007643bd25e227 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007643bd1faa55 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007643b7a642fe in ?? () from /usr/lib/gio/modules/libdconfsettings.so
#4  0x00007643bd22f026 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 8 (Thread 0x764394e006c0 (LWP 9691) "nautilu:disk$0"):
#0  0x00007643bbd5ba19 in ?? () from /usr/lib/libc.so.6
#1  0x00007643bbd5e479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x0000764395ce3fbe in ?? () from /usr/lib/libvulkan_intel.so
#3  0x0000764395ccab5c in ?? () from /usr/lib/libvulkan_intel.so
#4  0x0000764395ce3f1d in ?? () from /usr/lib/libvulkan_intel.so
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6
--Type <RET> for more, q to quit, c to continue without paging--

Thread 7 (Thread 0x764397e006c0 (LWP 9693) "nautilus"):
#0  0x00007643bbdac733 in clock_nanosleep () from /usr/lib/libc.so.6
#1  0x00007643bbdb8827 in nanosleep () from /usr/lib/libc.so.6
#2  0x000076438a7ff0b7 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#3  0x000076438ac30bd6 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#4  0x000076438a7fee04 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 6 (Thread 0x764389c006c0 (LWP 9694) "[vkrt] Analysis"):
#0  0x00007643bbd5ba19 in ?? () from /usr/lib/libc.so.6
#1  0x00007643bbd5e7e2 in pthread_cond_timedwait () from /usr/lib/libc.so.6
#2  0x000076438a7fc8dc in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#3  0x000076438ac402c7 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#4  0x000076438a7fee04 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7643892006c0 (LWP 9695) "[vkcf] Analysis"):
#0  0x00007643bbd5ba19 in ?? () from /usr/lib/libc.so.6
#1  0x00007643bbd5e479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x000076438a7fc87c in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#3  0x000076438ac2af55 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#4  0x000076438a7fee04 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 4 (Thread 0x76437d4006c0 (LWP 9697) "[vkps] Update"):
#0  0x00007643bbd5ba19 in ?? () from /usr/lib/libc.so.6
#1  0x00007643bbd5e7e2 in pthread_cond_timedwait () from /usr/lib/libc.so.6
#2  0x000076438a7fc8dc in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#3  0x000076438ac1656d in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#4  0x000076438a7fee04 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#5  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#6  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

--Type <RET> for more, q to quit, c to continue without paging--
Thread 3 (Thread 0x76437ca006c0 (LWP 9699) "nautilus"):
#0  0x00007643bbd5ba19 in ?? () from /usr/lib/libc.so.6
#1  0x00007643bbd5e7e2 in pthread_cond_timedwait () from /usr/lib/libc.so.6
#2  0x000076438a7fc8dc in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#3  0x000076438ad3188c in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#4  0x000076438ad1e9b6 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#5  0x000076438a7fee04 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#6  0x00007643bbd5f39d in ?? () from /usr/lib/libc.so.6
#7  0x00007643bbde449c in ?? () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7643b9d5da00 (LWP 9673) "nautilus"):
#0  0x00007643bbdd663d in poll () from /usr/lib/libc.so.6
#1  0x000076438a810883 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#2  0x000076438ac279e9 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#3  0x000076438ac27af3 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#4  0x000076438ac51736 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#5  0x000076438abf42ca in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#6  0x000076438abe7206 in ?? () from /usr/lib/libnvidia-glcore.so.560.35.03
#7  0x00007643bcaa4b22 in ?? () from /usr/lib/libgtk-4.so.1
#8  0x00007643bcaa573c in ?? () from /usr/lib/libgtk-4.so.1
#9  0x00007643bca3effc in ?? () from /usr/lib/libgtk-4.so.1
#10 0x00007643bca47752 in ?? () from /usr/lib/libgtk-4.so.1
#11 0x00007643bca9b1aa in ?? () from /usr/lib/libgtk-4.so.1
#12 0x00007643bd08182a in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#13 0x00007643bd0b2565 in ?? () from /usr/lib/libgobject-2.0.so.0
#14 0x00007643bd0a2ca9 in ?? () from /usr/lib/libgobject-2.0.so.0
#15 0x00007643bd0a2f32 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#16 0x00007643bd0a2ff4 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#17 0x00007643bca7edd8 in ?? () from /usr/lib/libgtk-4.so.1
#18 0x00007643bd1fca0a in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x00007643bd1fb559 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x00007643bd25e157 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x00007643bd1faa55 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0x00007643bc3d8cb6 in g_application_run () from /usr/lib/libgio-2.0.so.0
#23 0x00005e1e55a2ca18 in ?? ()
#24 0x00007643bbcf0e08 in ?? () from /usr/lib/libc.so.6
#25 0x00007643bbcf0ecc in __libc_start_main () from /usr/lib/libc.so.6
--Type <RET> for more, q to quit, c to continue without paging--
#26 0x00005e1e55a2ca95 in ?? ()

tekstryder wrote:

Shino wrote:
1) GSK_RENDERER....
While ensuring an X11 session, please post the output of
GSK_DEBUG=renderer nautilus

GSK_DEBUG=renderer nautilus
** Message: 21:56:28.552: Connecting to org.freedesktop.Tracker3.Miner.Files
Not using 'GskVulkanRenderer': platform is not Wayland
Not using GL: OpenGL support disabled via GDK_DISABLE
Using renderer 'GskVulkanRenderer' for surface 'GdkX11Toplevel'
[1]    10313 terminated  GSK_DEBUG=renderer nautilus

Last edited by Shino (2024-11-01 20:58:09)

seth · 2024-11-01 21:01:27

I think the idea is to check whether nautilus actually cares about the GSK_RENDERER environment.
https://gitlab.gnome.org/GNOME/gtk/-/is … te_2246854 but there're also people reporting the ngl doesn't work…

Last edited by seth (2024-11-01 21:02:43)

tekstryder · 2024-11-01 21:01:36

Gusfit wrote:

Oh and thanks for the link to that issue tekstryder

I do not use X11, just a casual observer who spends too much time upstream haha.

Shino wrote:

GSK_DEBUG=renderer nautilus
** Message: 21:56:28.552: Connecting to org.freedesktop.Tracker3.Miner.Files
Not using 'GskVulkanRenderer': platform is not Wayland
Not using GL: OpenGL support disabled via GDK_DISABLE
Using renderer 'GskVulkanRenderer' for surface 'GdkX11Toplevel'
[1]    10313 terminated  GSK_DEBUG=renderer nautilus

Based on symptoms, it certainly appears you are both affected by the issue I noted.

Specifically check this section: https://gitlab.gnome.org/GNOME/gtk/-/is … te_2247535
EDIT: Linked to the wrong section, ooops. Fixed.

There are two related fixes from GTK and Nautilus in the works:

• https://gitlab.gnome.org/GNOME/gtk/-/co … 1296425d31
• https://gitlab.gnome.org/GNOME/nautilus … uests/1641

Last edited by tekstryder (2024-11-01 21:05:12)

Arch Linux

#1 2024-10-31 16:25:17

Maximizing nautilus freezes gnome.

#2 2024-10-31 18:28:43

Re: Maximizing nautilus freezes gnome.

#3 2024-10-31 22:07:44

Re: Maximizing nautilus freezes gnome.

#4 2024-10-31 22:55:44

Re: Maximizing nautilus freezes gnome.

#5 2024-10-31 23:46:16

Re: Maximizing nautilus freezes gnome.

#6 2024-11-01 07:53:11

Re: Maximizing nautilus freezes gnome.

#7 2024-11-01 10:07:59

Re: Maximizing nautilus freezes gnome.

#8 2024-11-01 10:15:51

Re: Maximizing nautilus freezes gnome.

#9 2024-11-01 12:52:36

Re: Maximizing nautilus freezes gnome.

#10 2024-11-01 15:48:54

Re: Maximizing nautilus freezes gnome.

#11 2024-11-01 16:15:16

Re: Maximizing nautilus freezes gnome.

#12 2024-11-01 18:10:54

Re: Maximizing nautilus freezes gnome.

#13 2024-11-01 18:59:12

Re: Maximizing nautilus freezes gnome.

#14 2024-11-01 19:05:25

Re: Maximizing nautilus freezes gnome.

#15 2024-11-01 19:20:56

Re: Maximizing nautilus freezes gnome.

#16 2024-11-01 19:28:25

Re: Maximizing nautilus freezes gnome.

#17 2024-11-01 19:28:37

Re: Maximizing nautilus freezes gnome.

#18 2024-11-01 19:48:15

Re: Maximizing nautilus freezes gnome.

#19 2024-11-01 20:29:42

Re: Maximizing nautilus freezes gnome.

#20 2024-11-01 20:35:21

Re: Maximizing nautilus freezes gnome.

#21 2024-11-01 20:45:27

Re: Maximizing nautilus freezes gnome.

#22 2024-11-01 20:51:32

Re: Maximizing nautilus freezes gnome.

#23 2024-11-01 20:52:18

Re: Maximizing nautilus freezes gnome.

#24 2024-11-01 21:01:27

Re: Maximizing nautilus freezes gnome.

#25 2024-11-01 21:01:36

Re: Maximizing nautilus freezes gnome.

Board footer