[Bug 680106] New: emacs gives warning when started
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c0 Summary: emacs gives warning when started Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mjambor@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- When I start emacs in X, it writes the following to the standard error: ---------------------------------------------------------------------- (emacs:30395): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Abnormal program termination spawning command line `dbus-launch --autolaunch=f2e42fa76d380fe9ded6ae94493eec15 --binary-syntax --close-stderr': ) (emacs:30395): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. ---------------------------------------------------------------------- I use the gtk emacs under fluxbox. However, I've been able to google a workaround. When I add the following to my ~/.xinitrc before launching fluxbox, the problem goes away: ---------------------------------------------------------------------- if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then eval `dbus-launch --sh-syntax --exit-with-session` fi ---------------------------------------------------------------------- Nevertheless, I really think an editor that is being launched here and there so often should not do this unless something really bad is happening. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c1 Stephan Barth <stephan.barth@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stephan.barth@novell.com --- Comment #1 from Stephan Barth <stephan.barth@novell.com> 2011-03-20 08:06:27 UTC --- I have the same issue and I also think that dbus shouldn't be used by default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |werner@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c2 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@novell.com AssignedTo|werner@novell.com |vuntz@novell.com --- Comment #2 from Dr. Werner Fink <werner@novell.com> 2011-04-14 09:46:06 UTC --- Ahmm ... dbus *is* used by default, otherwise the gtk/glib will not work correct. This is not a problem of emacs as emacs only uses the gtk interface[1]. If you do not like this use emacs-x11 or set the variable EMACS_TOOLKIT to "x11" and export it. [1]: werner/emacs> bzgrep g_spawn_sync emacs-23.2.tar.bz2 werner/emacs> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c3 Bob Vickers <R.Vickers@cs.rhul.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |R.Vickers@cs.rhul.ac.uk --- Comment #3 from Bob Vickers <R.Vickers@cs.rhul.ac.uk> 2011-11-10 15:10:35 UTC --- I have encountered this bug too, but it is not 100% reproduceable. I suspect it only happens when the system is busy. If dbus is running and DBUS_SESSION_BUS_ADDRESS is set then I believe emacs works OK. If DBUS_SESSION_BUS_ADDRESS is not set then emacs invokes dbus-launch but does not reliably read its exit status. Here are some messages with dbus-launch verbosity enabled: $ export DBUS_VERBOSE=1 $ emacs (emacs:11682): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Abnormal program termination when spawning command line `dbus-launch --autolaunch=b8b7eef26650346e3ef6a596486b954a --binary-syntax --close-stderr': 11685: Autolaunch enabled (using X11).\n11685: --exit-with-session automatically enabled\n11685: Connected to X11 display ':1047.0'\n11685: dbus-daemon is already running. Returning existing parameters.\n11685: dbus-launch exiting\n) dbus-launch has correctly discovered an existing dbus session, but emacs thinks it has failed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c4 --- Comment #4 from Bob Vickers <R.Vickers@cs.rhul.ac.uk> 2011-11-11 10:02:00 UTC --- I just wanted to add another comment after a night's sleep! This bug has been reported in many other forums and it seems to me that people are missing the point by focusing on making sure that dbus is running. But actually it shouldn't matter whether dbus is running, and it shouldn't matter whether DBUS_SESSION_BUS_ADDRESS is set in the environment. What other products (e.g. evince) do is run dbus-launch with the --autolaunch option. This will search for an existing dbus and if it does not find one start a new one. emacs attempts to do the same but sometimes it does not work, and the message suggests it is because SIGCHLD is being ignored. I am guessing that whether it works depends on how busy the network and CPUs are. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c5 --- Comment #5 from Dr. Werner Fink <werner@suse.com> 2011-11-11 10:47:05 UTC --- (In reply to comment #3)
nm -D usr/bin/emacs-gtk | grep g_spawn_sync
.. if a library like to starts dbus it may sets the signal handler for SIGCHILD temporary -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c6 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |werner@suse.com --- Comment #6 from Vincent Untz <vuntz@suse.com> 2012-05-15 15:24:46 UTC --- I'm not sure why this got assigned to me. Why is g_spawn_sync() related to this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c7 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|werner@suse.com | --- Comment #7 from Dr. Werner Fink <werner@suse.com> 2012-05-15 15:54:39 UTC --- You are one the glib2 maintainer and as the list os.gnome.maintainers@gmail.com is more like a black hole I've choosen you as you have been the most entries in the change log.
From the point of the emacs using gtk I can do exactly nothing ... beside not using gtk and there not using glib2.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c8 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |werner@suse.com --- Comment #8 from Vincent Untz <vuntz@suse.com> 2012-05-15 16:04:00 UTC --- My point is that it's not glib nor gtk that is starting the dbus daemon. So why would this be a glib/gtk issue? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c9 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|werner@suse.com | --- Comment #9 from Dr. Werner Fink <werner@suse.com> 2012-05-15 16:49:03 UTC --- ?? AFAICS from above the message happens if dbus daemon is *not* running. Affacted are users with their personal .xinitrc or .xsession to avoid dbus and other helpers. The question is: Why does this warning happen out from glib2 without any need? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c10 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |werner@suse.com --- Comment #10 from Vincent Untz <vuntz@suse.com> 2012-05-15 17:09:54 UTC --- If the bug is about this warning: === (emacs:30395): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. === Then the warning clearly says that it's a bug in the program, ie in emacs... So what am I missing? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c11 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|werner@suse.com | --- Comment #11 from Dr. Werner Fink <werner@suse.com> 2012-05-15 17:21:59 UTC --- That emas does not call the function g_spawn_sync() but glib2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c12 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |werner@suse.com --- Comment #12 from Vincent Untz <vuntz@suse.com> 2012-05-15 17:33:29 UTC --- Does emacs call g_spawn_command_line_sync()? I'm pretty sure glib doesn't call g_spawn_sync() itself (except through g_spawn_command_line_sync()). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c13 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|werner@suse.com | --- Comment #13 from Dr. Werner Fink <werner@suse.com> 2012-05-16 06:58:38 UTC --- A bzgrep does not find this: werner/emacs> bzgrep -c g_spawn emacs-23.3b.tar.bz2 0 werner/emacs> bzgrep -ci g_spawn emacs-23.3b.tar.bz2 0 any further macro/function/callback for which I can grep for? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c14 --- Comment #14 from Vincent Untz <vuntz@suse.com> 2012-05-16 07:50:45 UTC --- Hrm, g_spawn_command_line_sync() is actually called once by gio, and this is to start dbus when there's no session bus. So that'd be a gio bug, indeed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c15 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.gnome.org/ | |show_bug.cgi?id=676167 --- Comment #15 from Vincent Untz <vuntz@suse.com> 2012-05-16 14:19:44 UTC --- I filed https://bugzilla.gnome.org/show_bug.cgi?id=676167 upstream for this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=680106 https://bugzilla.novell.com/show_bug.cgi?id=680106#c16 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Component|Other |Other Resolution| |FIXED Product|openSUSE 11.4 |openSUSE 12.1 OS/Version|Other |openSUSE 11.4 --- Comment #16 from Vincent Untz <vuntz@suse.com> 2012-07-09 15:50:18 UTC --- Okay, it seems there's no proper way to remove those warnings on 11.4. Based on my testing back in May, though, I was not seeing the warning on later releases. As this is no major deal, I think it's fine to leave it this way for 11.4, and mark as fixed for later releases. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com