You can launch any program with a different language by setting the LC_MESSAGES
environment variable (or LANG
to include other regional settings besides display language such as sort order, number and date formatting, etc).
$ LANG=en_US gnome-terminal
Keep in mind that anything you launch FROM that terminal will inherit the language. If you specifically want a program to run with your you could start it up with:
$ LANG=de_DE program_to_run_in_german
Have this problem on fedora 17, latest updates, exact same message in audit.log.
Had this happen a few days ago and again just now, tried repeatedly starting gnome-terminal from gnome menu, awn and alt-f2, audit.log shows the same message, one for each attempt.
Logging out of gnome shell and logging back in fixed the issue.
Pretty sure this isn't due to hardware that went bad, not seeing any other unexplained issues.
So far it seems to happen after previously closing gnome-terminal but I couldn't reproduce it by attempting to repeat the session after a reboot.
Have installed xterm now and will try run gnome-terminal from there if it happens again and report back.
To the OP: those kernel messages are purely informational and do not indicate any problem, they are most likely unrelated.
Edit: Running gnome-terminal from xterm after encountering this bug gave the following output:
$ gnome-terminal
GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
GConf Error: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
**
ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
Aborted
A quick Google search revealed this related bug report.
I was able to workaround the problem (without having to interrupt my session) by killing gconfd-2
$ killall -5 gconfd-2
$
Gnome will restart gconfd-2 automatically.
Best Answer
Straight from the "Troubleshooting" section of the nosh Guide, under the "GNOME Terminal refuses to start" heading:
Note that the GNOME Terminal server is the
org.gnome.Terminal
service started, indirectly via the DBUS Broker, under your per-user service manager. It runs a program namedgnome-terminal-server
which is actually what provides the terminal emulator. It is not thegnome-terminal
client command that you are directly running, which is just a control program for that server.Since there are so many varied ways in which the DBUS broker can be invoked, exactly how you do this is beyond the scope of this answer.
org.gnome.Terminal
service sets a UTF-8 locale.How you do this depends from what per-user service manager you have. With nosh service management, for just one example, one just tweaks its service environment directory (
$HOME/.config/service-bundles/services/org.gnome.Terminal/service/env
) with theset-service-env
command:If you have systemd doing per-user service management, for another example, you'll need to inject an
Environment=
setting into/lib/systemd/user/gnome-terminal-server.service
using the "drop-in" mechanism, which the systemd people do not document for per-user services.You of course make sure that that locale actually exists as a locale definition on your system, too. It is no good adjusting to UTF-8 locale if there is no such UTF-8 locale definition present.
Further reading