Bug 1401364

The transparency looks like it might be a vte bug.  There are no error messages, even in debug mode, when I set my window to be transparent.  Maybe egmont can pipe in here?

This looks like the error for hide_windows

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/terminatorlib/window.py", line 231, in on_focus_out
    self.hidefunc()
TypeError: 'NoneType' object is not callable

Which looks like an upstream bug in terminator.  I'll do some more poking.

How exactly are you hiding the window?

It looks like the hide_window keybinding only works if keybinder3 is installed, and it's using X11, not Wayland.

I tried altering the code to work under wayland, but I just get a segmentation fault.  I'll see about opening an upstream bug

The transparency issue could be the same as https://bugs.launchpad.net/terminator/+bug/1647052.

Created attachment 1229301 [details]
config

Configuration file from Terminator. With the same configuration v 0.98-4.fc25 works, v 1.90-1.fc25 doesn't

The transparency stuff was not quite ready for the gtk3 rewrite, but is coming in the next release.  

The hide_window functionality under wayland is a tougher nut to crack, as Terminator thinks its running on wayland even when running under X11 in Fedora, so we have to figure out:

1.  How to detect wayland properly.
2.  How to get global keybinding functionality under wayland.  

I haven't forgotten about you, it's just a matter of finding the time to sit down and figure it all out.

Can you confirm this has been fixed in the latest release 1.91?

Updated to terminator-1.91-2.fc25 and transparency doesn't work. I use X11 and not wayland.

Same on fedora 26 - no transparency. I also use X11. Downgrade is not posible:

"Package terminator of lowest version already installed, cannot downgrade it."

To make sure we're speaking of the same transparency feature: Preferences->Profiles->Background->Transparent background. This works for me here, I'm not able to reproduce this. My terminator version is terminator-1.91-2.fc26.noarch.

Is terminator printing something when you start it from a terminal? Maybe also try to start it with --debug to see more detailed output.

Yes, we're speaking about the same transparency feature. I'm using terminator in openbox and X11.


Starting terminator from a terminal gives this output:

** (terminator:2471): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-3DS3B0Lpml: Connection refused


Here the output with --debug:

terminator --debug

** (terminator:2210): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-3DS3B0Lpml: Connection refused
ConfigBase::__init__: Borg::__init__: Preparing borg state for ConfigBase
noclass::get_config_dir: Found config dir: /home/mad/.config
ConfigBase::load: looking for config file: /home/mad/.config/terminator/config
ConfigBase::load: config validated successfully
ConfigBase::load: ConfigBase::load: Processing section: global_config
ConfigBase::load: ConfigBase::load: Processing section: keybindings
ConfigBase::load: ConfigBase::load: Processing keybindings: hide_window
ConfigBase::load: ConfigBase::load: Processing keybindings: cycle_prev
ConfigBase::load: ConfigBase::load: Processing keybindings: help
ConfigBase::load: ConfigBase::load: Processing keybindings: close_window
ConfigBase::load: ConfigBase::load: Processing keybindings: group_tab
ConfigBase::load: ConfigBase::load: Processing keybindings: resize_left
ConfigBase::load: ConfigBase::load: Processing keybindings: broadcast_all
ConfigBase::load: ConfigBase::load: Processing keybindings: rotate_ccw
ConfigBase::load: ConfigBase::load: Processing keybindings: move_tab_left
ConfigBase::load: ConfigBase::load: Processing keybindings: go_right
ConfigBase::load: ConfigBase::load: Processing keybindings: new_tab
ConfigBase::load: ConfigBase::load: Processing keybindings: resize_right
ConfigBase::load: ConfigBase::load: Processing keybindings: resize_down
ConfigBase::load: ConfigBase::load: Processing keybindings: toggle_zoom
ConfigBase::load: ConfigBase::load: Processing keybindings: scaled_zoom
ConfigBase::load: ConfigBase::load: Processing keybindings: zoom_in
ConfigBase::load: ConfigBase::load: Processing keybindings: paste
ConfigBase::load: ConfigBase::load: Processing keybindings: full_screen
ConfigBase::load: ConfigBase::load: Processing keybindings: prev_tab
ConfigBase::load: ConfigBase::load: Processing keybindings: split_vert
ConfigBase::load: ConfigBase::load: Processing keybindings: ungroup_all
ConfigBase::load: ConfigBase::load: Processing keybindings: broadcast_off
ConfigBase::load: ConfigBase::load: Processing keybindings: cycle_next
ConfigBase::load: ConfigBase::load: Processing keybindings: rotate_cw
ConfigBase::load: ConfigBase::load: Processing keybindings: insert_number
ConfigBase::load: ConfigBase::load: Processing keybindings: insert_padded
ConfigBase::load: ConfigBase::load: Processing keybindings: zoom_out
ConfigBase::load: ConfigBase::load: Processing keybindings: broadcast_group
ConfigBase::load: ConfigBase::load: Processing keybindings: go_prev
ConfigBase::load: ConfigBase::load: Processing keybindings: layout_launcher
ConfigBase::load: ConfigBase::load: Processing keybindings: close_term
ConfigBase::load: ConfigBase::load: Processing keybindings: new_terminator
ConfigBase::load: ConfigBase::load: Processing keybindings: ungroup_tab
ConfigBase::load: ConfigBase::load: Processing keybindings: go_left
ConfigBase::load: ConfigBase::load: Processing keybindings: copy
ConfigBase::load: ConfigBase::load: Processing keybindings: edit_tab_title
ConfigBase::load: ConfigBase::load: Processing keybindings: go_down
ConfigBase::load: ConfigBase::load: Processing keybindings: reset
ConfigBase::load: ConfigBase::load: Processing keybindings: search
ConfigBase::load: ConfigBase::load: Processing keybindings: go_up
ConfigBase::load: ConfigBase::load: Processing keybindings: resize_up
ConfigBase::load: ConfigBase::load: Processing keybindings: next_tab
ConfigBase::load: ConfigBase::load: Processing keybindings: split_horiz
ConfigBase::load: ConfigBase::load: Processing keybindings: zoom_normal
ConfigBase::load: ConfigBase::load: Processing keybindings: move_tab_right
ConfigBase::load: ConfigBase::load: Processing keybindings: new_window
ConfigBase::load: ConfigBase::load: Processing keybindings: edit_window_title
ConfigBase::load: ConfigBase::load: Processing keybindings: group_all
ConfigBase::load: ConfigBase::load: Processing keybindings: go_next
ConfigBase::load: ConfigBase::load: Processing keybindings: edit_terminal_title
ConfigBase::load: ConfigBase::load: Processing keybindings: reset_clear
ConfigBase::load: ConfigBase::load: Processing keybindings: toggle_scrollbar
ConfigBase::load: ConfigBase::load: Processing section: profiles
ConfigBase::load: ConfigBase::load: Processing profile: default
ConfigBase::load: ConfigBase::load: Processing section: layouts
ConfigBase::load: ConfigBase::load: Processing layouts: default
ConfigBase::load: ConfigBase::load: Processing section: plugins
Config::set_profile: Config::set_profile: Changing profile to default
Config::connect_gsetting_callbacks: GSetting connects for system changes
noclass::parse_options: OptionParse::parse_options: command line options: {'nodbus': None, 'classname': None, 'working_directory': None, 'select': None, 'fullscreen': None, 'layout': 'default', 'debug_classes': None, 'version': None, 'role': None, 'forcedicon': None, 'config': '/home/mad/.config/terminator/config', 'profile': None, 'debug_methods': None, 'maximise': None, 'debug': 1, 'borderless': None, 'new_tab': None, 'hidden': None, 'dummy': None, 'execute': None, 'geometry': None, 'command': None, 'forcedtitle': None}
ConfigBase::load: ConfigBase::load: config already loaded
Config::set_profile: Config::set_profile: Changing profile to default
Config::connect_gsetting_callbacks: GSetting connects for system changes
ConfigBase::get_item: ConfigBase::get_item: dbus found in globals: True
function::with_proxy: dbus client call: new_window_cmdline
function::with_proxy: dbus client call: new_tab_cmdline
function::with_proxy: dbus client call: new_window
function::with_proxy: dbus client call: new_tab
function::with_proxy: dbus client call: hsplit
function::with_proxy: dbus client call: vsplit
function::with_proxy: dbus client call: get_terminals
function::with_proxy: dbus client call: get_window
function::with_proxy: dbus client call: get_window_title
function::with_proxy: dbus client call: get_tab
function::with_proxy: dbus client call: get_tab_title
DBusService::__init__: Borg::__init__: Preparing borg state for DBusService
DBusService::prepare_attributes: Checking for bus name availability: net.tenshu.Terminator20x1a6021154d881c
DBusService::prepare_attributes: bus name unavailable: net.tenshu.Terminator20x1a6021154d881c
noclass::<module>: Unable to become master process, operating via DBus
noclass::<module>: Requesting a new window


The DBUS-env looks

env |grep DBUS
TERMINATOR_DBUS_NAME=net.tenshu.Terminator20x1a6021154d881c
TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

Even if I'm afraid that this will not fix the transparency-issue, could you check if you have dbus-python installed on your system? For completeness, here are the dbus-packages I have installed here:

abrt-dbus-2.10.3-1.fc26.x86_64
python3-dbus-1.2.4-6.fc26.x86_64
dbus-python-1.2.4-6.fc26.x86_64
libdbusmenu-16.04.0-2.fc26.x86_64
libdbusmenu-gtk3-16.04.0-2.fc26.x86_64
dbus-libs-1.11.14-1.fc26.x86_64
python-slip-dbus-0.6.4-6.fc26.noarch
dbus-1.11.14-1.fc26.x86_64
dbus-glib-0.108-2.fc26.x86_64
python3-slip-dbus-0.6.4-6.fc26.noarch
dbusmenu-qt-0.9.3-0.12.20150604.fc26.x86_64
dbus-x11-1.11.14-1.fc26.x86_64

Probably we've just pointed out a missing dependency so far at least.

Have you tried to enable/disable the transparency in debug mode? Does that probably give some more information?

dbus-python is installed. These are the dbus-packages on my systems (have the issue on my desktop and my laptop):

dbus-1.11.14-1.fc26.x86_64
dbus-devel-1.11.14-1.fc26.x86_64
dbus-glib-0.108-2.fc26.x86_64
dbus-libs-1.11.14-1.fc26.x86_64
dbusmenu-qt-0.9.3-0.12.20150604.fc26.x86_64
dbus-python-1.2.4-6.fc26.x86_64
dbus-sharp-0.8.1-1.fc26.x86_64
dbus-sharp-glib-0.6.0-1.fc26.x86_64
dbus-x11-1.11.14-1.fc26.x86_64
dleyna-connector-dbus-0.2.0-8.fc26.x86_64
libdbusmenu-16.04.0-2.fc26.x86_64
libdbusmenu-gtk3-16.04.0-2.fc26.x86_64
ndesk-dbus-0.6.1a-22.fc26.x86_64
python3-dbus-1.2.4-6.fc26.x86_64
python3-slip-dbus-0.6.4-6.fc26.noarch
python-slip-dbus-0.6.4-6.fc26.noarch
qt-qdbusviewer-4.8.7-28.fc26.x86_64

> Have you tried to enable/disable the transparency in debug mode? Does that probably give some more information?

I've tried it, but there are no messages/informations.

Here is the debug-output when activating trancparency:

noclass::get_config_dir: Found config dir: /home/mad/.config
ConfigBase::set_item: ConfigBase::set_item: Setting background_type=transparent (profile=default, plugin=None)
ConfigBase::save: ConfigBase::save: saving config
ConfigBase::save: ConfigBase::save: Processing section: global_config
ConfigBase::save: ConfigBase::save: Processing section: keybindings
ConfigBase::save: ConfigBase::save: Processing profile: default
ConfigBase::save: ConfigBase::save: Processing layout: default
noclass::get_config_dir: Found config dir: /home/mad/.config
ConfigBase::get_item: ConfigBase::get_item: extra_styling found in globals: True
ConfigBase::get_item: ConfigBase::get_item: handle_size found in globals: -1
Terminal::reconfigure: Terminal::reconfigure
Signalman::remove_signal: realize not registered for <class 'gi.repository.Vte.Terminal'>
Signalman::remove_signal: removing <class 'gi.repository.Vte.Terminal'>::child-exited
ConfigBase::get_item: ConfigBase::get_item: exit_action found in profile default: close
ConfigBase::get_item: ConfigBase::get_item: exit_action found in profile default: close
Signalman::new: connected <class 'gi.repository.Vte.Terminal'>::child-exited to <function <lambda> at 0x7f95e7b796e0>
ConfigBase::get_item: ConfigBase::get_item: encoding found in profile default: UTF-8
ConfigBase::get_item: ConfigBase::get_item: word_chars found in profile default: -,./?%&#:_
ConfigBase::get_item: ConfigBase::get_item: mouse_autohide found in profile default: True
ConfigBase::get_item: ConfigBase::get_item: backspace_binding found in profile default: ascii-del
ConfigBase::get_item: ConfigBase::get_item: delete_binding found in profile default: escape-sequence
ConfigBase::get_item: ConfigBase::get_item: use_system_font found in profile default: False
ConfigBase::get_item: ConfigBase::get_item: font found in profile default: Monospace 10
ConfigBase::get_item: ConfigBase::get_item: allow_bold found in profile default: True
ConfigBase::get_item: ConfigBase::get_item: use_theme_colors found in profile default: False
ConfigBase::get_item: ConfigBase::get_item: foreground_color found in profile default: #ffffff
ConfigBase::get_item: ConfigBase::get_item: background_color found in profile default: #000000
ConfigBase::get_item: ConfigBase::get_item: background_type found in profile default: transparent
ConfigBase::get_item: ConfigBase::get_item: background_darkness found in profile default: 0.28
ConfigBase::get_item: ConfigBase::get_item: inactive_color_offset found in globals: 0.8
Terminal::reconfigure: ('fgcolor_inactive set to: RGB(%s,%s,%s)', 1.0, 1.0, 1.0)
Terminal::reconfigure: ('fgcolor_inactive set to: RGB(%s,%s,%s)', 0.8, 0.8, 0.8)
ConfigBase::get_item: ConfigBase::get_item: palette found in profile default: #000000:#cc0000:#00cc00:#aa5500:#6b6bea:#aa22aa:#00cccc:#ffeedd:#444444:#d61f06:#00ff00:#aa5500:#6b6bea:#ff00ff:#00ffff:#ffffff

When I set

export NO_AT_BRIDGE=1

the first dbus-warning disappears but

DBusService::__init__: Borg::__init__: Preparing borg state for DBusService
DBusService::prepare_attributes: Checking for bus name availability: net.tenshu.Terminator20x1a6021154d881c
DBusService::prepare_attributes: bus name unavailable: net.tenshu.Terminator20x1a6021154d881c

is still visable.


I also tried to reproduce the behavior in gnome (fedora running in a vm) but here i could not reproduce it.

Ok - that is funny. On the same VM where terminator has transparency in gnome it does not have transparency in openbox.

What I dis:
- Setup a fedora 26 vm
- log into gnome X11 desktop 
- install terminator
- set transparency
-> works as it should
- install openbox
- logout from gnome
- login into openbox (as the same user)
- open terminator
-> no transparency
- logout from openbox
- login into gnome
- open terminator
-> transparency works

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.