GNOME Bugzilla – Bug 775654
send_infos_cb: No such interface 'org.gtk.vfs.Enumerator' on object at path /org/gtk/vfs/client/enumerator/1 (g-dbus-error-quark, 19)
Last modified: 2016-12-16 08:56:35 UTC
I have a strange problem, which I also reported downstream at Gentoo[1]. The symptom is that for some users on some machines some GNOME programs don't show any windows anymore, most importantly nautilus and evince. I have two machines both running Gentoo Linux with GNOME 3.20. On machine A everything works perfectly and I did not see this bug. On machine B for one user (betty) nautilus does not show any window and evince only shows the preview window when opened, but not the document window. For another user, nautilus works fine, but evince does not. Every time this bug occurs, this message is logged to the journal, so I assume it is related somehow: Nov 16 10:30:01 leonardo org.gtk.vfs.Daemon[22106]: ** (process:22552): WARNING **: send_infos_cb: No such interface 'org.gtk.vfs.Enumerator' on object at path /org/gtk/vfs/client/enumerator/1 (g-dbus-error-quark, 19) Anyone has an idea what might be going on there? Any help is greatly appreciated. Please let me know if I should provide more information. [1] https://bugs.gentoo.org/show_bug.cgi?id=599964
The problem started after upgrading from GNOME 3.18 to 3.20, btw.
Thanks for your bug report. I suppose it would be rather some other issue and those warnings are just a side-effect... I have no idea in what case it may return the "No such interface" errors. It returns usually "The connection is closed" if enumeration is closed prematurely, or the application exited, or so... I haven't got much ideas, how we can debug this. We need to figure out where it hangs, so you can try obtaining backtraces, and/or latrace outputs for Nautilus/Evince?
Created attachment 341536 [details] Output of strace nautilus where the bug occurs Thanks for your comment. I'll start by attaching the output of "strace nautilus" for both, the working and the faulty execution.
Created attachment 341537 [details] Output of strace nautilus where the bug does NOT occur
I will try to gather further output of gdb and latrace soon.
Nautilus strace contains the following criticals: (nautilus:24632): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Not sure it is related to your issue, but it might be fixed by the Bug 773383. Can't you test it with the patch from that bug? Or you can obtain backtrace for this error instead (if you always see those criticals). You can do it by the following command: pkill nautilus; G_DEBUG=fatal-criticals gdb nautilus --ex "set confirm off" --ex "run" --ex "thread apply all backtrace" --ex "quit" > backtrace It is possible to find several similar bug reports using google, but without any obvious solution. I saw various workarounds, but probably no real solution: kill the nautilus and run it again, reinstall the nautilus package, disable tracker... Maybe it is duplicate of Bug 749207, Bug 738546... Carlos, don't you have any idea what's wrong?
I solved the problem! It was my fault... Suddenly, the problem was gone for nautilus, but still occurred sometimes with evince (in like 50% of the cases), but I could not determinne the circumstances leading to the problem. Then I wanted to do a screencast which shows the problem and by doing this, I found out the real cause of this strange issue: The screencast video showed two screens, and sometimes the evince windows appearead on the second screen! I ran xrandr and the scales fell from my eyes: The single monitor was not only connected by DVI, but also via VGA! I have no idea how or when this happened, but I feel really stupid now... Sorry I bothered you with this and thank you very much for your input!
Thanks for your comment. Still I really wonder why you get those warnings, because I am not able to reproduce them, but it isn't anything critical. I am going to remove those warnings anyway...
Before noticing the real cause of my problem I upgraded the machine to GNOME 3.22 and I never got that log message ever since. So I guess whatever caused seems to be fixed.
Ok, thanks for the notice. It is possible that also something changed in dbus and that is why I can't reproduce exactly this error. Anyway, I have pushed commit 8dec4b1 recently into master, which suppresses those warnings...
Great!