[SOLVED] gnome-terminal doesn't start

loorke · 12-11-2016, 11:59 AM

gnome-terminal doesn't start for a week. When I run it from other terminal (e.g. urxvt) there isn't any output information. Process continues to exist until I press Ctrl+C. I'm not sure, but looks like it happened after update.

Distro: ArchLinux
Desktop: xmonad
gnome-terminal --version output: "Терминал GNOME 3.22.1 Используется VTE версии 0.46.1 +GNUTLS"
locale (it's fine):

Code:

LANG=ru_RU.UTF-8
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES=ru_RU.UTF-8
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=

c0wb0y · 12-11-2016, 04:36 PM

Post output of:

Code:

printenv

Try to regenerate locales

loorke · 12-11-2016, 05:12 PM

Quote:

Originally Posted by c0wb0y

Post output of:

Code:

printenv

Try to regenerate locales

printenv:

Code:

LANG=ru_RU.UTF-8
DISPLAY=:0.0
COLORTERM=truecolor
MM_CHARSET=UTF-8
MOZ_PLUGIN_PATH=/usr/lib/mozilla/plugins
XDG_VTNR=2
XDG_SESSION_ID=c2
USER=loorke
PWD=/home/loorke
HOME=/home/loorke
MAIL=/var/spool/mail/loorke
WINDOWPATH=2
SHELL=/bin/bash
VTE_VERSION=4601
TERM=xterm-256color
LC_MESSAGES=ru_RU.UTF-8
SHLVL=3
XDG_SEAT=seat0
WINDOWID=27262979
_JAVA_AWT_WM_NONREPARENTING=1
LOGNAME=loorke
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
XDG_RUNTIME_DIR=/run/user/1000
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/common/scripts
_=/usr/bin/printenv

Quote:

Try to regenerate locales

I've already tried.

c0wb0y · 12-11-2016, 10:11 PM

Environment looks alright. Are you able to lauch other GTK3-based apps like gedit no prob? Or you can create a dummy account and test from there, just in case some of your .g* configs are messed up. Or if you feel like digging deeper, you can strace it.

loorke · 12-12-2016, 04:41 AM

Quote:

Originally Posted by c0wb0y

Environment looks alright. Are you able to lauch other GTK3-based apps like gedit no prob? Or you can create a dummy account and test from there, just in case some of your .g* configs are messed up. Or if you feel like digging deeper, you can strace it.

Quote:

Are you able to lauch other GTK3-based apps like gedit no prob?

Absolutely. Gedit is my favourite code editor.

Quote:

Or you can create a dummy account and test from there, just in case some of your .g* configs are messed up.

I've already tried too.

Quote:

Or if you feel like digging deeper, you can strace it.

Can you explain?

c0wb0y · 12-12-2016, 02:04 PM

You open xterm, then launch strace with gnome-terminal as the argument. For example,

Code:

strace -o mystrace.txt gnome-terminal

be warned with gazillion system calls. You can, though specify which syscalls you want (eg -e open,write ...). If you can try that and post the output here, people here might be able to help you out.

loorke · 12-12-2016, 04:59 PM

Quote:

Originally Posted by c0wb0y

You open xterm, then launch strace with gnome-terminal as the argument. For example,

Code:

strace -o mystrace.txt gnome-terminal

be warned with gazillion system calls. You can, though specify which syscalls you want (eg -e open,write ...). If you can try that and post the output here, people here might be able to help you out.

The recent system update fixed it. Thanks for your time.