[SOLVED] GNOME terminal is completely blank

When I open the gnome terminal, it is completely blank, not the usual "$ user@computer". Any ideas?
Last edited by r42xer (2012-04-28 00:37:04)

Haha, silly me, the text was black on a black background. Gee do I feel stupid. Closing.

Similar Messages

Terminal is COMPLETELY blank. Sits at "login" and nothing works.

Opened up Terminal.app and the window is *completely blank*. There is nothing in it whatsoever. Bash never started. The title bar simply says "Terminal — login — 80x24". I can type whatever I want in the Terminal window like it's a text document and nothing happens. If I restart the computer, this seems to fix the problem, but it seems to only be a temporary fix as the issue happens again soon after.
Any ideas?

I found that, even if "Command (complete path):" is selected (instead of "Default login shell (/usr/bin/login)") the shell is not started directly by Terminal but started via login (as "login -pfq username /path/to/the/shell").
Start Activity Monitor.app, and select "All Processes" from the pop-up menu at the top of the window. Then click onece or twice on the "PID" (title of the left most column of the process list) so that the process list is sorted in the decreasing order of pid (largest pid at the top of the list).
Also start Console.app, and select "All Messages" (or system.log) in in the left pane of the window.
Now start Terminal.app (or open a new window in Terminal). In my case, Activity Monitor shows "login", "zsh" (=my shell) and "taskgated" are started in this order, and taskgated terminates in a 10 seconds or so. Console.app shows the message like
DATE TIME login[62364]: USER_PROCESS: 62364 ttys000
Do you get this kind of log message? Any other messages (errors) in Console.app?
If you think "login" is hanging, then, in Activity Monitor, select the process "login" in the process list, push the "Inspect" button at the top of the window, and push the "Sample" button; you may need to enter the admin password. Then you will see some info about what the "login" is doing now. Does this give any hit about what is going wrong?
Are you using any special settings or third party software which might interfere with the authentication process?

[Solved] Gnome-terminal does not start (fresh install)

Whenever I install gnome-terminal, I have the following message displayed:
(gconftool-2:28984): GConf-WARNING **: Client failed to connect to the D-BUS daemon:/usr/bin/dbus-launch terminated abnormally without any error message
Then whenever I launch gnome-terminal I have this message:
** (gnome-terminal:1102): CRITICAL **: atk_bridge_adaptor_cleanup: assertion `inited' failed
The problem seems to be related to dbus. I have even tried guake which complains explicitly about "No D-BUS daemon running".
Systemctl is telling me that d-bus is up and running.
Any help appreciated.
Info:
- Linux arch64-vbox 3.6.9-1-ARCH #1 SMP PREEMPT Tue Dec 4 08:04:10 CET 2012 x86_64 GNU/Linux
- systemctl --all | grep error
auditd.service error inactive dead auditd.service
display-manager.service error inactive dead display-manager.service
plymouth-quit-wait.service error inactive dead plymouth-quit-wait.service
plymouth-start.service error inactive dead plymouth-start.service
rc-local.service error inactive dead rc-local.service
syslog.service error inactive dead syslog.service
Cheers,
Last edited by PierreR (2012-12-05 20:16:59)

Solved with the latest dbus upgrade (dbus-core removal)

[SOLVED] gnome-terminal 3.12 won't start

After I upgraded to gnome 3.12, I my terminal refused to start with the error "Message did not receive a reply". It turns out that the issue was that I had previously installed vte3-mosh-fix from the AUR, and the new version of gnome-terminal was incompatible with that old version of vte3. Running "pacman -S vte3" fixed the problem for me. (And I think that mosh fix has been incorporated into the latest version too.) Posting in case anyone else runs into this.

The patch was indeed merged into the upstream, it's the only reason I haven't updated the PKGBUILD.

[SOLVED] gnome-terminal won't start

Well, first of all good day and thanks in advance.
gnome-terminal is not launching. I get:
ERROR:terminal-app.c:1433:terminal_app_init: assertion failed: (app->system_font_desc != NULL)
This started with no particular trigger, and now i am using aterm, but i like better gnome-terminal, so any help would be appreciated.
Last edited by evildrake (2009-07-24 16:37:48)

Seems like a font issue, try this:
gnome-terminal --tab-with-profile=Default
Else you can try editing the settings using gconf-editor.

[SOLVED] gnome-terminal initial path

Recently my gnome-terminal initial path became "/" instead of my home. How can I fix that? I haven't this problem when I use xterm or log in out of Xorg.
Thank you
Last edited by cemsbr (2009-04-16 06:26:20)

cemsbr wrote:
Recently my gnome-terminal initial path became "/" instead of my home. How can I fix that? I haven't this problem when I use xterm or log in out of Xorg.
Thank you
Then it's probably gnome/gnome terminal's fault.
Check every settings tab in gnome-terminal..,see if there's an option to set initial folder path
If not, adding a "cd ~/" on the first line of your ~/.bashrc could also do the trick (assuming you use bash as a shell)
Last edited by Wra!th (2009-04-15 14:02:43)

( SOLVED )gnome-terminal, su, sudo, gksu, gksudo does not work

Hello,
In my fresh installed gnome3 graphical environment, in gnome-terminal, I can not gain root access.
I've tried diverse su commands.
1. su command, ends with:
su -
Password:
su: Authentication failure
2. sudo command, ends with:
sudo -l
[sudo] password for root:
Sorry, try again.
[sudo] password for root:
Sorry, try again.
[sudo] password for root:
sudo: 2 incorrect password attempts
Of course - each time, I typed correct password.
In my sudoers file, group wheel ( into which belongs user I logged in ) has permissions to execute any command.
3. gksudo with debug:
gksudo -ld gnome-terminal
No ask_pass set, using default!
xauth: /tmp/libgksu-stbGos/.Xauthority
STARTUP_ID: gksudo/gnome-terminal/879-0-Bex_TIME0
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: root
cmd[7]: --
cmd[8]: gnome-terminal
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
sudo: 1 incorrect password attempt
xauth: /tmp/libgksu-stbGos/.Xauthority
xauth_env: /var/run/gdm/auth-for-tangram-9JYTNt/database
dir: /tmp/libgksu-stbGos
I've been asked for my password, not root, after typing I get "incorrect password attempt", if I type root pwd I get the same.
4. Same with this command:
gksu -ld gnome-terminal
No ask_pass set, using default!
xauth: /tmp/libgksu-SBPcOB/.Xauthority
STARTUP_ID: gksu/gnome-terminal/1028-0-Bex_TIME0
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: root
cmd[7]: --
cmd[8]: gnome-terminal
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
sudo: 1 incorrect password attempt
xauth: /tmp/libgksu-SBPcOB/.Xauthority
xauth_env: /var/run/gdm/auth-for-tangram-6RCSoJ/database
dir: /tmp/libgksu-SBPcOB
In multi-user-mode I can login to root account.
Last edited by tangram (2013-12-23 08:42:09)

tangram wrote:
Hurrican, ok, there is no need to install antother terminal, as I wrote it did not work also in xterm.
Yesterday evening, tired and sad that gk(su|sudo) still does not work,
as the "last chance idea", I logged in into multi-user mode ( init level 3 ) and changed root's password,
then loged in into graphical mode ( init level 5 ), start gnome-terminal and suddenly ... command "su -" started to work.
By the way, similar solution ( but with chroot ) has suggested Gulver in his post ( this thread, answer #2 ).
The question is, why root's password, set during install, after finished installation is recognized in text mode, but not im graphical ?
First root's password was really simple, like "dog4356", without any national chars.
You're right. I don't even have xterm installed so I guess I just singled out gnome-terminal and forgot that xterm also wasn't working.
Forgive me for my shaky advice. Like you I've been super busy, and sweating out a fever of 102 degrees (that's Fahrenheit no my
blood wasn't boiling ). Anyways, glad you got it working. After reading over the whole thread and thinking about it for a little bit, I
can't really make a good guess as to what was happening.
I'm sure you probably had tried this, but you could have typed the password out in the command line so you could see it. If there was
something wrong with it, it would have shown up there as well. If it was perfectly fine, then it would have been very, very weird.
The important thing is you got it working.
Merry Christmas.

(solved) gnome-terminal opening as xterm

So when I open gnome-terminal, the title shows xterm instead. What's causing this?
Last edited by zephyrus17 (2008-12-26 12:52:07)

a) Yes
b) I did pacman -S gnome-terminal and it just asked for a reinstall
EDIT: I think a restart fixed it. Thanks, anyway.
Last edited by zephyrus17 (2008-12-26 12:48:28)

[Solved] Gnome-Terminal Not Working

I recently installed Arch Linux and got the Gnome Gui working but when I tried to open the default terminal it started to load then quickly ended I looked a "solution" which said to type gnome-terminal into xterm so I did and it came up with:
(process:766): Gtk-WARNING **: Locale not supported by C library. Using the fall back 'C' Locale.
Error constructing proxy for org.gnome.Terminal:/org/Terminal/Factory0:for calling StartServiceByName for org.gnome.terminal: GDbus.error:org.freedeop.Dbus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with statu
and with I typed locale -a I got this:
Locale: Cannot set LC_CTYPE to default locale: No such file or directory
and it said the same thing for LC_MESSAGES and LC_COLLATE
Last edited by Satanic Command Line (2015-01-07 22:30:55)

jasonwryan wrote:
Satanic Command Line wrote:Sadly none of the solutions made a difference
Not helpful. Provide some detail as to what you tried; don't be a help vampire...
I have /etc/locale.conf
# localectl set-locale LANG="en_US.UTF-8" that didn't work
(Try to regenerate locales first:
# locale-gen
And then:
# localectl set-locale LANG="en_US.UTF-8"
reboot) that didn't work
localectl set-locale didn't work
(quoting alphabeat) All you have to do is edit /etc/locale.gen(/quote) didn't work
Sorry if this is unhelpful

[SOLVED] Gnome 3 is completely messed graphically

Hello guys
I already searched for a similar problem in the forum but I was not able to find any.
Here is the context : my workstation is completely up to date and is installed with Gnome 3 and systemd (no wild initscripts in legacy mode). My configuration is most of all the defaults. My wallpaper was picked in those bundled with Gnome 3 installation, and the only settings changed are details like behavior when closing the lid and timeouts for hibernation and screen shutdown.
I've got a lot of mess since the last update of Gnome 3. My first though was "the next update will fix it" but this so expected next update did not come in weeks. The symptoms are as follows : when I have a windowed application (I mean, not in fullscreen), the background is plain white, harmful for the eyes. If I try to move or resize the window, the old one remains printed on the background, as if only the window was refreshing. The whole thing is blinking. It is the same when I close a fullscreen window : it stays printed on the background. If there is other windows, they get a weird black or dark blue (it depends, but I dont know on what it depends) thick border (about 10, 15 pixels). At some time, the wallpaper turns black and shows my desktop icons (which I dont care since I dont want any icon, the previous behavior was fine for me). When I shutdown the session or the computer, the wallpaper turns blue (juste like a BSOD ) and the Gnome menus are blurry and interlaced with some of that blue.
I dont have any crash though, and no problem when staying fullscreen in a single application. I loved Gnome 3 so far and it works perfectly well in the previous version. But I may need to switch for something else if I cant find a fix . Any help will be welcome. Deep thanks by advance.
Last edited by duckie (2013-12-05 21:44:06)

Okay, you gonna kill me, I just found out the problem. I was using lxdm instead of gdm because gdm was buggy. I switched back to gdm and everything seems fine. Hope this can help someone someday. I guess writing it down helped me to find it.

[Solved]urxvt does not search the font for emojis while gnome-terminal

Hi, I'm using urxvt and am having some problems setting up fonts. These are my URxvt parameters specifying the fonts
URxvt*font: xft:Inconsolata-dz for Powerline:style=Semibold:pixelsize=14:antialias=true:hinting=slight, \
xft:PowerlineSymbols:pixelsize=14:antialias=true:hinting=slight, \
xft:Symbola:pixelsize=14:antialias=true:hinting=slight
Now, the emojis from Symbola does not appear and it only appears as a box
The same thing when opened in Gnome-terminal properly displays the emojis
Also, I have tried starting urxvt with the following options
urxvt -fn "xft:Symbola"
and it works but as you see Symbola is not a font for your terminal.
What am I doing wrong here? I've check my previous lines and it is right. Do you guys have any ideas? Much appreciated. I have also tried with other posts stating that Urxvt cannot display symbols properly and have tried them all. If I've missed any please let me know. The strange thing is that it works for Gnome-terminal and Urxvt with only Symbola fonts
Last edited by decryptedepsilon (2014-07-12 02:40:24)

bch24 wrote:
Make sure the System Locale is set to utf-8 locale.
This sometimes is the issue.
Many thanks for your reply, I've checked the system locale is proper. I think I have found the solution.
I think the official rxvt-unicode faq and documentation here states that rxvt-unicode drops pixels while showing some fonts because different fonts use different height and width. In this particular case, Symbola font is too wide and the default letterSpace does not allow it to display correct. If -letsp parameter is set to 4, it is displaying but with about a half pixel missing
The specific parameters for .Xresources
URxvt*font: xft:Inconsolata-dz for Powerline,xft:Symbola
URxvt*letterSpace: 4
And this gives this which technically solves the issue
The documentation clearly states the following
All of this requires that fonts do not lie about character sizes, however: Xft fonts often draw glyphs larger than their acclaimed bounding box, and rxvt-unicode has no way of detecting this (the correct way is to ask for the character bounding box, which unfortunately is wrong in these cases).
I guess the first thing one should do is to check the documentation thoroughly of the official project page rather than searching countless forums where people have discussed stuff based on trial and error. I guess that's a classic rookie mistake and I feel very good that I'm moving past the rookie phase

[SOLVED] Gnome 3.12 : gnome terminal does not run anymore

I had the following message when trying to run gnome-terminal after updating to 3.12:
Error creating terminal: Message did not receive a reply (timeout by message bus)
I have found a fix, so I'll share it with the community. The problem was that I had vte3-mosh-fix installed from the aur, version 0.34.9 and that gnome-terminal now requires vte3 0.36.0.
Switching to the official vte3 package fixes the issue.

Thank you for posting the solution. I would have never even remembered that I had installed that mosh fix, let alone thought to remove it.

[SOLVED] Gnome 3.4 - Super+R to launch terminal

I added a new shortcut to "gnome-terminal" as Ctrl+Alt+T on keyboard shortcuts configuration program. However, I can only set it to <C-A-t> (control+alt+t), and not to Super+R, or Super+T, or Super+ENTER.
It used to work on Gnome 3.2? Should I report this on bugzilla, or does anybody have any idea of what my issue really is? Thank you.
Last edited by ephan (2012-04-24 13:28:22)

is reported https://bugzilla.gnome.org/show_bug.cgi?id=659899

[solved] Internal padding in gnome-terminal

Hi there,
Is there a way to define an internal padding in gnome-terminal of Gnome 3.8?
The output is too close to the window borders and I would like to have them placed a bit more inside.
At the moment it looks like that: http://i.imgur.com/QlVPrFf.png
Thanks!
EDIT:
To move the terminal output away from the window borders create the stylesheet ~/.config/gtk-3.0/gtk.css with the following setting:
TerminalScreen {
-VteTerminal-inner-border: 10px 10px 10px 10px;
Last edited by orschiro (2013-05-26 20:15:42)

On most recent Gnome 3.16 we need to create the stylesheet ~/.config/gtk-3.0/gtk.css with the following setting:
VteTerminal,
TerminalScreen {
padding: 10px 10px 10px 10px;
-VteTerminal-inner-border: 10px 10px 10px 10px;
Ref.: https://wiki.archlinux.org/index.php/GN … e_terminal

Root in Gnome Terminal has wrong $PATH [Solved]

Hello
wehn i open a Root terminal in gnome the Root user hasn't the full PATH (only /usr/ucb:/bin:/usr/bin:/etc)
I have no idea what is wrong.
Thanks for every answer.
Last edited by ZeroCool (2009-10-12 21:06:34)

Stefan Husmann wrote:This bug is confirmed by a user in german forum. B, you are right, but a normal su should take the environment from the underpriviliged user who switches to root, and not to something insane. Where does this /usr/ucb come from? The path does not even exist.:/
Big Thanks for this information Now i know what is it.
When i use
gksudo -l gnome-terminal
i became
[zerocool@bruel ~]$ gksudo -l gnome-terminal
(gksudo:15810): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
(gksudo:15810): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
(gksudo:15810): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
(gksudo:15810): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

[SOLVED] GNOME terminal is completely blank

Similar Messages

Maybe you are looking for