Running Terminator on Windows 10 bash
Hi. I've been using Terminator for a long time in Linux. Now that Windows has its Linux/bash subsystem, I'd like to also have it available there. I understand that's a whole different matter, and there may be no interest in supporting or troubleshooting. If so, no worries, but I figured I'd let smarter people than I take a stab at it. I'll explain what I've done so far, then where things stand.
I have installed xming as an X11 server. It does work-- little things like xeyes, etc work well. I also have gtk, and can run programs that depend on it, such as gnome-calculator. I have installed terminator via apt-get. It was a massive installation, with loads of dependencies, and appeared to install correctly. I created a config file in ~/.config/
[global_config]
[keybindings]
[profiles]
[[default]]
scrollback_
font = Monospace 8
use_system_font = False
background_
[layouts]
[[default]]
[[[child1]]]
type = Terminal
parent = window0
[[[window0]]]
type = Window
parent = ""
[plugins]
After all of that, I tried starting it by running /usr/bin/
Any suggestions on how I might get this working? I know that running this under Windows Ubuntu/Bash is pretty bleeding-edge. But, I'd truly love to have this running. Terminator has been good to me on Linux, and I'd like to also have it in Windows. Many thanks in advance.
#### Run attempt output:
# /usr/bin/terminator
/usr/share/
self.
/usr/share/
self.
/usr/share/
self.
/usr/share/
self.
process 11585: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
(terminator:11585): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
process 11585: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
(terminator:11585): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
process 11585: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
(terminator:11585): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
process 11585: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
(terminator:11585): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
process 11585: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
(terminator:11585): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
PluginRegistry:
process 11585: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
(terminator:11585): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File "/usr/bin/
TERMINATOR.
File "/usr/share/
window, terminal = self.new_window()
File "/usr/share/
terminal = maker.make(
File "/usr/share/
output = func(**kwargs)
File "/usr/share/
return(
File "/usr/share/
self.
File "/usr/share/
self.
File "/usr/share/
title_font = pango.FontDescr
File "/usr/share/
'/desktop/
glib.GError: No D-BUS daemon running
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Terminator Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Andrew for more information if necessary.