You are not logged in.
I recently set up a fresh arch64 installation with gnome and I've noticed a very strange bug. When opening files through nautilus which launch in either eog or gedit (possibly others, but those are the only 2 I've found), if an instance of that application is running already, the cursor will stay at the working status (the circle with lines going around it in adwaita) for about 15 seconds. It only shows this cursor when the mouse is over a gnome application such as nautilus, eog, any window decoration, or the desktop. The cursor acts normally over all other windows as well as gedit's text area. This only happens when opening a file (launching the application itself through nautilus doesn't trigger it) and only if an instance is already running.
I set about trying to fix this, so I started running nautilus through gdb and found something rather curious. When you select a file in nautilus, it will launch a thread pool thread ("pool" 0x00007ffff4694cc1 in pthread_cond_timedwait@@GLIBC_2.3.2). When you open a file, it launches another one and immediately closes it. When you open a file that launches in eog or gedit while another instance is running, it launches a new thread then immediately closes the thread which is launched when you select a file. The thread launched at the launch of the application doesn't close for 15 seconds or so, and the cursor stays at the waiting status until it closes.
Is this something that could be related to my config or arch, or is this an upstream bug? Does anyone (everyone?) else running gnome 3 experience this behavior?
Edit: Ah, I've just discovered others are also experiencing this. My googling turned up nothing related, but I discovered this (https://bbs.archlinux.org/viewtopic.php?id=130229) thread browsing through after posting this. I'm going to go ahead and assume this is a nautilus bug and see if I can find any indication they're aware of it.
Last edited by XionZui (2012-08-26 11:54:24)
Offline