Fail to launch Terminator

[Michael Heuberger]

Hi there

When I run the command `terminator` inside the terminator, I got these warnings:

$ terminator
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::sm-connect after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::display after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::default-icon after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)

** (terminator:4855): WARNING **: Binding '<Shift><Control><Alt>a' failed!
Unable to bind hide_window key, another instance/window has it.
<Window object at 0x1fd48c0 (terminatorlib+window+Window at 0x1f9e0b0)> is not in registered window list

Maybe these are bugs? Or something is wrong with the default config?

Cheers
Michael

[Surya Narayan Dev (snd-surya)]

Hi all,

I am getting the following error:

/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::sm-connect after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::display after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::default-icon after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
Floating point exception

Have been searching for a way out for a very long time. Seems like a bug to me now.
Any way out?

Thanks
Dev

[Miguel Dias (migueldiasbr)]

Just FYI, I'm getting the same error when I have something on Custom Command like: ls -l

I was opening Terminator with a custom layout: terminator -l teste

[Yanbing Liu (841216767-5)]

I have the same problem when I start terminator in terminal, my system is Linux MInt:
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::sm-connect after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::display after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
/usr/share/terminator/terminatorlib/terminator.py:87: Warning: Attempt to add property GnomeProgram::default-icon after class was initialised
  self.gnome_program = gnome.init(APP_NAME, APP_VERSION)
Warning: python-keybinder is not installed. This means the hide_window shortcut will be unavailable
Unable to bind hide_window key, another instance/window has it.
How to fix this problem?

[Stephen Boddy (stephen-j-boddy)]

Hi Bug subscribers, this is the maintainer (Steve Boddy) of Terminator, who took over from Chris.

In case you were not aware there has been a new release 0.98 of Terminator in the last few days which has many changes, fixes and updates. We also have an ongoing GTK3 port which uses a much more up-to-date libvte.

Even with the ~50 issues closed by that release, and discounting the ~90 outstanding wishlist items, we still have an unwieldy 95 bugs. With the oldest approaching it's 6th birthday and some that haven't seen any updates in nearly 5, it is time for a purge.

My intention is to try and get this list down to a minimum, and for that I need your help.

First I'm going to work through, oldest to newest, setting bugs to Incomplete, pending confirmation that they are still an issue. If after a month there is no feedback, the issue will get closed as Invalid. Here's where you come in. I can't always reproduce, or setting up (i.e. other distros) to even test takes a long time, so I'm going to try crowdsourcing this.

1. Get the latest release. Is it still an issue? If yes, set the confirmed-0.98 tag. For bonus points follow the guide http://gnometerminator.blogspot.com/2015/09/so-you-want-to-try-terminator-gtk3.html and see if the GTK3 branch has same issue, and set the confirmed-gtk3 or notaffected-gtk3 tag.

2. Can you reproduce with an empty/default config file? You can pass "-g temp_config" to do this without affecting your existing config. If you already have Terminator running, you'll need to pass -u as well to disable the DBus.

3. If able to, can you reproduce with another user/guest account?

4. If the issue does not already have clear, precise instructions to reproduce with minimal setup/steps, add them.

5. Put as much info about what you are running.
   * Software/library versions (libvte, gtk, pango, cairo, distro, desktop environment, language)
   * Screens (single or multi)
   * Any unusual / custom packages or configs that might be interacting.

6. If possible attach the config file, unless the issue also happens with an empty one, but mention that.

7. Attach the "-d" debug output from 0.98.

Some common things that cause incidents.

* Strange sizing issues or rapidly shrinking windows - Try turning off Window geometry hints.
* Input (esp. broadcasting duplicate chars etc) problems - Try killing IBus.
* Hand editing of the config file can cause various issues - Due to misunderstanding, incorrect structure or typos.
* Some issues are actually in libvte - This is why testing GTK3 is so important.
* segfaults - Unfortunately these are dying inside the C libraries, and it is usually beyond me to fix those.

Many thanks for your assistance, and hopefully this will get us closer to a bug-free Terminator.

[Alessander Botti Benevides (alessanderbotti)]

This bug occurs when calling Terminator from the gnome-terminal. It does not prevents Terminator from starting.

1. I am using Terminator 0.98 (from ppa:gnome-terminator on Ubuntu 14.04) and I set the confirmed-0.98 tag.

2. I could reproduce with both "terminator -u -g temp_config" and "terminator -g temp_config", though -g is not listed as an option by "man terminator".

3. I could reproduce it in a guest account.

4. Call terminator from gnome-terminal.

5.1.
* distro: Ubuntu 14.04;
* desktop environment: the default one (Unity);
* language: pt-br (Brazilian Portuguese);
* how can I check the versions of libvte, gtk, pango and cairo?
5.2. Single screen;
5.3. Nope. Could you can suggest any for me to check?

6. The issue also happens with "terminator -g temp_config", though -g is not listed as an option by "man terminator".

7. Please see the attached file.

P.S.: As an unrelated comment, I would suggest the Terminator team to include an explicit advice in the manual stating that one have to activate DBus server in the preferences of Terminator in order for the flag --new-tab to work.

Thanks,
Alessander

[Stephen Boddy (stephen-j-boddy)]

OK, so this is errors generated by the underlying libraries, and mostly seem to be as a result of running under "alien" non-gnome desktop environments.

Correct me if I'm wrong, but no one ever said this actually cause a bug, it's just that some warnings appear. The only problem is the universal hide shortcut does not get registered. That's not something we can do anything about, because it is a limitation of the library that it can only register the shortcut in the gnome environment.

Going to mark this as Won't Fix, as I I'm not prepared to spawn a ever-increasingly complex web of attempts to detect the desktop and trying to account for all the permutations. If someone else were to spend the time figuring out how to detect every desktop environment, compositor, utility libraries etc, etc, and come up with a patch to handle them all gracefully, then I'll look at it. For now we'll just live with some warnings getting spit out to the stdout/err.