[Possible bug] I can not start mate-terminal

[rubyFeedback]

I compiled mate-terminal from the latest git source right now. It compiled.

But when I do "./mate-terminal" nothing happens. No output. Not starting
mate-terminal.

I did strace it and I get this:

futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[PIPE], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f150c14c8d0}, {sa_handler=SIG_IGN, sa_mask=[PIPE], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f150c14c8d0}, 8) = 0
futex(0x7f150c5a06c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
newfstatat(AT_FDCWD, "/home/Temp/bus", 0x7ffdd1249970, 0) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/dbus/machine-id", O_RDONLY) = 6
newfstatat(6, "", {st_mode=S_IFREG|0644, st_size=33, ...}, AT_EMPTY_PATH) = 0
read(6, "30c2dceb2c51bd16caa94e626318ac58"..., 33) = 33
close(6) = 0
pipe2([6, 7], 0) = 0
pipe2([8, 9], 0) = 0
pipe2([10, 11], 0) = 0
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f1508bf1e10) = 15692
close(11) = 0
read(10, "", 8) = 0
close(10) = 0

read(10, "", 8) = 0
close(10) = 0
close(7) = 0
close(9) = 0
poll([{fd=6, events=POLLIN|POLLERR|POLLHUP}, {fd=8, events=POLLIN|POLLERR|POLLHUP}], 2, -1) = 1 ([{fd=8, revents=POLLIN}])
read(8, "EOF in dbus-launch reading addre"..., 4096) = 51
poll([{fd=6, events=POLLIN|POLLERR|POLLHUP}, {fd=8, events=POLLIN|POLLERR|POLLHUP}], 2, -1) = 2 ([{fd=6, revents=POLLHUP}, {fd=8, revents=POLLHUP}])
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=15692, si_uid=0, si_status=1, si_utime=0, si_stime=0} ---
read(6, "", 4096) = 0
close(6) = 0
read(8, "", 4096) = 0
close(8) = 0
wait4(15692, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 15692
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}], 2, 0) = 1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\20\0\10\0\25\0\0\0_GTK_EDGE_CONSTRAINTSter", iov_len=32}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 32
poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\1\0\220\0\0\0\0\0L\2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x96a8a0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="+\0\1\0", iov_len=4}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 4
poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\1\0\221\0\0\0\0\0\f\0\340\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
getpid() = 15686
getpid() = 15686
exit_group(1) = ?
+++ exited with 1 +++

Perhaps this is related to some dbus issue on my system.

BUT!

Even in that case, mate-terminal should not silently quit. It should notify me why it
does not continue. Right now it just exits silently... which is not useful to find out
what is wrong here.

[thesquash]

Try closing any MATE Terminal windows you already have open, then press Alt-F2 (this pops up the "Run Application..." dialog). When that dialog pops up, type the path to the new mate-terminal binary (in your case, it looks like it'd be at something like /home/Temp/mate-terminal/mate-terminal, and click the "Run" button. If a terminal pops up now (and it's the latest version of the MATE Terminal -- check the Help menu -> About), then the only problem was that the new MATE Terminal only will open its own window if there isn't already another instance of the MATE Terminal running.