[opensuse] emacs woes
I saw a posting on this group recently saying that xemacs is about to be dropped, so decided I better start training my fingers to use emacs instead. Am running openSuSE 11.4 x86_64 and tried to fire off emacs and it barfed - emacs vsftpd.conf & [1] 22024 bigbang:/srv/ftp # 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: The connection is closed) g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. [1]+ Terminated emacs vsftpd.conf Can anyone decipher this for me and tell me how to help emacs feel better? Thanks much, Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 29, 2012 at 12:46:28PM -0800, Marc Chamberlin wrote:
I saw a posting on this group recently saying that xemacs is about to be dropped, so decided I better start training my fingers to use emacs instead. Am running openSuSE 11.4 x86_64 and tried to fire off emacs and it barfed -
emacs vsftpd.conf & [1] 22024 bigbang:/srv/ftp # 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: The connection is closed) g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
[1]+ Terminated emacs vsftpd.conf
Can anyone decipher this for me and tell me how to help emacs feel better? Thanks much, Marc...
Guess: you're using the default that is emacs-gtk and this one requires a running D-Bus. You may do export EMACS_TOOLKIT=x11 before starting emacs. But with this you'll see the Xaw3d API and not the modern GTK Look&Feel. Btw: using standard login should use dbus-launch ... for my personal ~/.xsession I'm using killall -u werner -q dbus-daemon exec -a dbus-launch dbus-launch --sh-syntax --exit-with-session fvwm2 as very last line. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 29, 2012 at 12:46:28PM -0800, Marc Chamberlin wrote:
I saw a posting on this group recently saying that xemacs is about to be dropped, so decided I better start training my fingers to use emacs instead. Am running openSuSE 11.4 x86_64 and tried to fire off emacs and it barfed -
emacs vsftpd.conf& [1] 22024 bigbang:/srv/ftp # 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: The connection is closed) g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
[1]+ Terminated emacs vsftpd.conf
Can anyone decipher this for me and tell me how to help emacs feel better? Thanks much, Marc... Guess: you're using the default that is emacs-gtk and this one requires a running D-Bus. You may do
export EMACS_TOOLKIT=x11
before starting emacs. But with this you'll see the Xaw3d API and not the modern GTK Look&Feel. Thanks Dr Werner for your help/reply, much appreciated! Yes, this does "fix" emacs up enough that it is healthy enough to run, and it certainly brings up emacs with a more primitive Look&Feel! Upon some further investigating I discovered I am only having this problem when I su to Root. Emacs works fine if I am running under my own user account. Interesting! Something about being the root user that emacs doesn't like?
Btw: using standard login should use dbus-launch ... for my personal ~/.xsession I'm using
killall -u werner -q dbus-daemon exec -a dbus-launch dbus-launch --sh-syntax --exit-with-session fvwm2
as very last line. Hmmmm I investigated both my own home dir and root's home dir and there is no such file called .xsession! Googling around tells me that there can be either a ~/.xsession or a ~/.xinitrc which are startup scripts for X. I have neither of these in my home dir or in root's But there is an xinitrc file in /etc/X11/xinit/ which I sort of grok as being
On 3/1/2012 1:36 AM, Dr. Werner Fink wrote: probably the same thing? I am NOT a Linux/openSuSE/X11 expert by any means, so am struggling to understand... Sorry if this is a newbie question... I did find a HUGE .xsession-errors file in my home dir which suggests there might be something very wrong with the configuration of X11 on my system? Googling also lead me to a bug submission about this file being so big, in the openSuSE bugs database, so perhaps there is a problem in my installation of openSuSE11.4? Anywise, since I don't have either of these files in my home dir, I am not sure what to do at this point. I will mention that my /home dir is located in a separate partition and I leave it alone and simply mount it as I migrate/upgrade from one version of openSuSE to the next. My understanding has been that this is an OK practice which allows me to easily migrate my personal settings/files from one version of openSuSE to the next. Is this perhaps too much to expect? or a broken model that no longer works?
Werner
Thanks again for your thoughts and reply... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 01, 2012 at 09:31:34AM -0800, Marc Chamberlin wrote:
Btw: using standard login should use dbus-launch ... for my personal ~/.xsession I'm using
killall -u werner -q dbus-daemon exec -a dbus-launch dbus-launch --sh-syntax --exit-with-session fvwm2
as very last line. Hmmmm I investigated both my own home dir and root's home dir and there is no such file called .xsession! Googling around tells me that there can be either a ~/.xsession or a ~/.xinitrc which are startup scripts for X. I have neither of these in my home dir or in root's But there is an xinitrc file in /etc/X11/xinit/ which I sort of grok as being probably the same thing?
If no personal ~/.xinitrc nor ~/.xsession exists then with the normal DM like kdm and gdm the system wide startup files are used and with kdm and gdm a dbus daemon should be launched otherwise the owner and permission handlings for e.g. devices will not work.
I am NOT a Linux/openSuSE/X11 expert by any means, so am struggling to understand... Sorry if this is a newbie question... I did find a HUGE .xsession-errors file in my home dir which suggests there might be something very wrong with the configuration of X11 on my system? Googling also lead me to a bug submission about this file being so big, in the openSuSE bugs database, so perhaps there is a problem in my installation of openSuSE11.4?
The ~/.xsession-errors will be created in /etc/X11/xdm/Xsession which then uses /etc/X11/xdm/sys.xsession. The messages in ~/.xsession-errors I guess are from a very verbose kde or gnome session.
Anywise, since I don't have either of these files in my home dir, I am not sure what to do at this point. I will mention that my /home dir is located in a separate partition and I leave it alone and simply mount it as I migrate/upgrade from one version of openSuSE to the next. My understanding has been that this is an OK practice which allows me to easily migrate my personal settings/files from one version of openSuSE to the next. Is this perhaps too much to expect? or a broken model that no longer works?
If do not know about ~/.xsession nor ~/.xinitrc you should not create them. Such files are for hard core wizards able to understand that for such personal files e.g. the kdm/gdm API will not work as the settings for e.g. the window manager will be overwritten ;) Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/29/2012 09:46 PM, Marc Chamberlin wrote:
I saw a posting on this group recently saying that xemacs is about to be dropped, so decided I better start training my fingers to use emacs instead. Am running openSuSE 11.4 x86_64 and tried to fire off emacs and it barfed -
emacs vsftpd.conf & [1] 22024 bigbang:/srv/ftp # GConf Error: Failed to contact configuration server;
Are you running Emacs as root and did a simple "su" and not a "su -"? That gives a different environment and might explain the issue. Does running emacs as normal user work fine - and does it work with "su -"? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/29/2012 09:46 PM, Marc Chamberlin wrote:
I saw a posting on this group recently saying that xemacs is about to be dropped, so decided I better start training my fingers to use emacs instead. Am running openSuSE 11.4 x86_64 and tried to fire off emacs and it barfed -
emacs vsftpd.conf & [1] 22024 bigbang:/srv/ftp # GConf Error: Failed to contact configuration server;
Are you running Emacs as root and did a simple "su" and not a "su -"? That gives a different environment and might explain the issue.
Does running emacs as normal user work fine - and does it work with "su -"?
Andreas Thanks Andreas for your reply! Well I learned something new, I did not know about the ability to do an "su -" I have always done a simple "su root" Anywise doing an "su -" appears to make emacs a bit healthier in
On 3/2/2012 1:46 AM, Andreas Jaeger wrote: that it does launch a window and starts up, but there is an error message that also gets chucked up in the process - bigbang:/etc # emacs vsftpd.conf (emacs:4435): 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=6b050dcfcaf094a4a7c7a30e000002ae --binary-syntax --close-stderr': ) I also observed that doing an "su -" relocated my current path to root's home directory and does not leave me in the directory from which I executed it. A bit of a PITA but I can live with it... To answer your other question, emacs works fine (at least no error messages are shown) when launched as a normal user, just launching it from the root user seems to give it fits... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andreas Jaeger <aj@suse.com> writes:
Are you running Emacs as root and did a simple "su" and not a "su -"? That gives a different environment and might explain the issue.
Also you don't need to start Emacs as root- you can use tramp. For example to open a file as root: ,---- | C-x C-f /sudo::/some_directory/some_file.txt `---- Charles -- "Oh, I've seen copies [of Linux Journal] around the terminal room at The Labs." (By Dennis Ritchie)
participants (4)
-
Andreas Jaeger -
Charles Philip Chan -
Dr. Werner Fink -
Marc Chamberlin