[SERVER-3997] Errors using EDITOR and emacs23-x in Ubuntu 11.04 Created: 02/Oct/11  Updated: 29/Feb/12  Resolved: 28/Nov/11

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tad Marshall Assignee: Tad Marshall
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Standard Terminal window in Ubuntu 11.04 32-bit running in VirtualBox 4.1.2 under Windows 7 64-bit


Operating System: Linux
Participants:

 Description   

This could be user error, but I'm getting a bunch of error messages that may be worth looking at. Or not.

In Ubuntu, I run the Terminal application from the Application/Accessories menu. Then I type "export EDITOR=/usr/bin/emacs23-x" which is the location of the X-windows version of EMACS in my setup. I can type "$EDITOR" and it runs EMACS.

But trying the example from the documentation in my 2.1.0-pre- copy of mongo (shell) built with "scons all", I get this:

tad@tad-VirtualBox:~$ echo $EDITOR

tad@tad-VirtualBox:~$ export EDITOR=/usr/bin/emacs23-x
tad@tad-VirtualBox:~$ $EDITOR // EMACS runs fine, no error messages
tad@tad-VirtualBox:~$ ./mongodb/mongo/mongo
MongoDB shell version: 2.1.0-pre-
connecting to: test
> f={}
{ }
> edit f

(emacs23-x:18731): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(emacs23-x:18731): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_object_add_weak_pointer: assertion `G_IS_OBJECT (object)' failed

(emacs23-x:18731): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(emacs23-x:18731): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_object_add_weak_pointer: assertion `G_IS_OBJECT (object)' failed

(emacs23-x:18731): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(emacs23-x:18731): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(emacs23-x:18731): GLib-GObject-CRITICAL **: g_object_add_weak_pointer: assertion `G_IS_OBJECT (object)' failed
> f

{ "key" : "value" }

>

The error messages from EMACS are all delivered as EMACS is started, and EMACS itself seems to be fine. I add the key:value pair, save the file and exit, and it worked. I see from the code in shell/dbshell.cpp that we're just calling ::system() with the EDITOR string followed by the filename, so maybe there's just something wrong with my copy of EMACS. On its splash screen, it says:

This is GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4)
of 2011-04-04 on rothera, modified by Debian
Copyright (C) 2010 Free Software Foundation, Inc.

The top of the changelog for my version of emacs23 says:

emacs23 (23.2+1-7ubuntu2) natty; urgency=low

  • debian/patches/no_cpp_multiarch_dir_mangling.diff: make sure cpp doesn't
    mangle our multiarch include path due to a built-in macro matching the
    architecture name. LP: #749270.

– Steve Langasek <vorlon@debian.org> Mon, 04 Apr 2011 08:51:24 +0000

in case this helps identify the code, but it's a version of EMACS listed in Ubuntu's Synaptic Package Manager's "Editors" section (4th line), so it's Canonical-supported code, and I am up-to-date on patches.



 Comments   
Comment by Tad Marshall [ 28/Nov/11 ]

I'm going to resolve this as "not a bug" or "nothing to fix". I'm now running Ubuntu in multiple versions in multiple virtual machines on multiple machines, and I see this flurry of Gtk messages on some and not others, and sometimes from the bash shell and sometimes only when launched by the mongo shell. Googling for the error messages indicates that this is a common problem with Gtk-based code, and not just Emacs, and the solutions are all over the map. So, we really can't do anything about this, and closing the bug is the right thing to do.

Comment by Mathias Stearn [ 31/Oct/11 ]

Any chance you get these messages when you launch emacs from the shell? It looks like those are just GTK messages and I know they can sometimes be "noisy" but just warnings.

Generated at Thu Feb 08 03:04:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.