Different results when executing command in terminator and default ubuntu terminal

Bug #1616216 reported by Micheal Talley
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Terminator
Incomplete
Low
Unassigned

Bug Description

When I run this command:
AWS_DEFAULT_REGION=us-east-1 AWS_ACCESS_KEY_ID=<access key here> AWS_SECRET_ACCESS_KEY=<secret key here> aws route53 list-resource-record-sets --hosted-zone-id <hosted zone id here>
from terminator, I get the following result:
[Errno 1] _ssl.c:510: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

However, on the same ubuntu machine, if I open up the default terminal the command is successful and returns the expected results. This appears to affect all aws cli commands. The aws cli is written in python, so I've also included my version of that and other associated libraries. However, why it would fail in terminator but successfully complete in the default terminal is puzzling. What is even more strange is that when you run terminator with the -d option, the same aws cli commands succeed.

Version of related packages:
Ubuntu 16.04, default Unity 7 desktop.
terminator 0.98
aws-cli/1.10.34
Python/2.7.11+
Linux/4.4.0-31-generic
botocore/1.4.24
OpenSSL 1.0.2g-fips 1 Mar 2016
certifi (2016.8.8)

Contents of my config file:
[global_config]
[keybindings]
[layouts]
  [[default]]
    [[[child1]]]
      parent = window0
      type = Terminal
    [[[window0]]]
      parent = ""
      type = Window
[plugins]
[profiles]
  [[default]]

Revision history for this message
Micheal Talley (mlt42) wrote :
Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

Yeah, I can't see how -d would make a difference, but as I don't understand why it fails in the first place... ¯\_(ツ)_/¯

The only thing I can think of to check is if the environment is slightly different. Have you compared the output from env before and after in both types of console, and looked for differences?

Another thing is, have you tried with the much newer gtk3 branch?

Don't know if this could be related: https://bugs.launchpad.net/terminator/+bug/1623427
Try the "Fix" and see if it starts working for you.

Changed in terminator:
status: New → Incomplete
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.