I recently installed manjaro gnome and after configuring locale settings, I found out that the terminal does not show up due to this error (from journalctl -xe):
(process:2410): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling
StartServiceByName for org.gnome.Terminal:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited
with status 1.
FIX:
So I went over internet and searched the error. I found out that it has something to do with /etc/locale.gen and /etc/locale.conf
It's actually on gnome's side and for whatever reasons related to their glib, they self-generated a corrupt locale.conf file and line "en_US.UTF-8 UTF-8" in file /etc/locale.gen has remained commented; so I uncommented that line and ran:
$ sudo locale-gen
After that, I edited line "LANG=en_US.utf8" to "LANG=en_US.UTF-8" in /etc/locale.conf file.
Finally, I ran gnome terminal and it came up!
Related
I am very new to linux. I am trying to build lammps open source software with user defined modules that require to build mpi executable on opensuse leap 15.1.
lammps - https://lammps.sandia.gov/doc/Build_make.html
It showed an error: mpicxx xommand not found.
after searching i did "sudo zypper in gcc-c++" and tried again.
same error
so I did "export PATH=$PATH:/usr/lib64/mpi/gcc/openmpi/bin"
and make mpi was successful and it built lmp_mpi executable but when i tried to run with lmp_mpi it showed following error:
error while loading shared libraries: libmpi_cxx.so.1: cannot open shared object file: No such file
so I wrote "export PATH=$PATH:/usr/lib64/mpi/gcc/openmpi/bin" in my bashrc file and ran again make mpi and tried again same error is shown.
I tried by installing mpich2 with yast same error is shown.
Then I tried by installing openmpi as shown here http://edu.itp.phys.ethz.ch/hs12/programming_techniques/openmpi.pdf
When I tried to build mpi again same error "mpicxx: Command not found error" and also when I open terminal following lines are written already.
bash: /home/surya/.bashrc: line 1: syntax error near unexpected token newline'
bash: /home/surya/.bashrc: line 1:export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/opt/openmpi/lib >'
Someone please help me I have been trying this for long time.
Thanks for the suggestions.
In gvim 8.1.1401 on Debian 10.4 when I open a file from Thunar with Right-click -> Open With -> Open with "gVim"
I have been getting an error popup:
Error
Error detected while processing /usr/share/vim/vim81/menu.vim:
line 166:
E121: Undefined variable: paste#paste_cmd
[OK]
When I open the same file from the command line with gvim /path/to/file it doesn't happen.
I don't get it launching normal vim from the command line either.
I tried uninstalling and re-installing all of my vim packages, in case it was picking up incompatible files from an old version. This didn't help.
I googled for the error and found various clues:
https://bugs.debian.org/388488
https://bugs.debian.org/520360
https://groups.google.com/d/topic/vim_use/x4R_QF-MXnE/discussion
GVIM - undefined variable: paste#paste_cmd?
They pointed me in the right direction to find it, i.e. an invalid runtimepath in ~/.vimrc, but were not the exact same error and didn't detail the solution I discovered.
By editing my ~/.vimrc and trying different things I tracked down the cause.
Because I couldn't find the answer online I'm sharing it here.
If you have:
set runtimepath=
in ~/.vimrc AND if that line does not include /usr/share/vim/vim81
then you will get the error.
If you don't have a ~/.vimrc you won't get the error.
If you don't have a runtimepath= entry you won't get the error.
If ~/.vimrc has a runtimepath= entry and it includes /usr/share/vim/vim81 in the path, then you won't get the error.
If this is still an issue in future versions of vim after 8.1 which doesn't have the vim81 directory, then the numbers will need to be updated to point to a valid directory for that version e.g. vim82 (or later)
NB: If the runtimepath in ~/.vimrc is correct, but vim81/autoload/paste.vim does not exist you will also get the error.
If vim81/autoload/paste.vim does exist, but the paste_cmd is commented out/deleted/corrupted, you will get the error (and an instance of it from each entry in vim81/autoload/paste.vim and any other files which refer to paste_cmd)
I hope this saves people time and prevents frustration!
I just upgraded to the current 64-bit Cygwin and X11 from old 32-bit versions from 2015. I'm getting some X-windows errors. The shortcut that starts X11 runs the following:
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
My ~/.startxwinrc is:
xrdb -load $HOME/.Xresources
xterm
I much prefer this over the default starting of X-windows in the absence of ~/.startxwinrc, which requires mousing down to the XDG icon in the system tray to popup a nested menu tree (especially since I'm always using a touchpad rather than a mouse).
xterm error messages
The above works fine, but if I issue the xterm command from an mintty terminal or xterm, I get the following message when the x-terminal appears:
xterm: cannot load font "-Misc-Fixed-bold-R-*-*-13-120-75-75-C-120-ISO10646-1"
The funny thing is, there is no such font in my Xresources file or the system Xresources file.
Very old ~/.Xresources:
xterm*font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
xterm*font1: -*-lucidatypewriter-medium-r-*-*-11-*-*-*-*-*-*-*
xterm*font2: -misc-fixed-medium-r-normal--13-120-75-75-c-70-iso8859-1
xterm*font3: -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso8859-1
xterm*font4: -*-lucidatypewriter-medium-r-*-*-14-*-*-*-*-*-*-*
xterm*font5: -b&h-lucidatypewriter-bold-r-normal-sans-14-*-*-*-m-*-*-*
xterm*font6: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-1
xterm*toolBar: false
! XTerm.toolBar: false
xterm*toolBar: false
!xterm*background: DarkBlue
xterm*background: rgb:00/00/66
xterm*foreground: White
Grepping the system Xresources file(s) yield nothing:
grep -i 13-120-75-75-C-120-ISO10646-1 /etc/X11/app-defaults/XTerm
grep -i 13-120-75-75-C-120-ISO10646-1 /etc/X11/app-defaults/*
gvim error messages
In addition to the mysterious xterm font problem, I get the following error starting gvim:
$gvim ~/tmp/tmp.txt
Can't resolve "wglCreateContextAttribsARB"
libGL error: required WGL extension WGL_ARB_multisample is missing
libGL error: required WGL extension WGL_ARB_multisample is missing
** (gvim:2058): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
The initial 3 lines only appear on the first invocation of gvim, while the last line (gvim WARNING) appears every time gvim is invoked, though with a different 4-digit number each time. These errors do not occur if I simply run vim. The errors do show up regardless of whether I have a custom /etc/vimrc or not (my vimrc runs slightly different code depending on whether it is called from vim or gvim). The closest thing I could find online to the gvim error is at this page, though it has to do with another app (and the cause is not tracked down).
Commonalities, and my 2 questions
The xterm font error and the gvim errors seem to be independent of whether I rely on default startxwin behaviour or on my ~/.startxwinrc. Depending on whether I launch xterm or gvim from the command line or the XDG menu, the error messages show up as bash shell command output or in ~/.xsession-errors.
Has anyone else observed this behaviour?
Can anyone suggest what else I can do to toubleshoot?
(I am not that familiar with X-11, as I am a a data analyst rather than a software developer.)
Addendum: I reinstalled all of the cygwin packages. The problem remains.
Addendum: Here are the font-like packages that I have installed:
$ cygcheck -c | grep -i font
adobe-source-code-pro-fonts 1.017-2 OK
dejavu-fonts 2.37-1 OK
fontconfig 2.12.6-1 OK
ghostscript-fonts-other 6.0-1 OK
inconsolata-fonts 1.010-1 OK
libfontconfig-common 2.12.6-1 OK
libfontconfig1 2.12.6-1 OK
libfontenc1 1.1.3-1 OK
libXfont2_2 2.0.3-1 OK
terminus-fonts 4.40-1 OK
texlive-collection-fontsextra 20180414-1 OK
texlive-collection-fontsrecommended 20180414-1 OK
urw-base35-fonts 20170801-5 OK
xfontsel 1.0.5-1 OK
xorg-x11-fonts-cyrillic 7.5-3 OK
xorg-x11-fonts-dpi100 7.5-3 OK
xorg-x11-fonts-dpi75 7.5-3 OK
xorg-x11-fonts-ethiopic 7.5-3 OK
xorg-x11-fonts-misc 7.5-3 OK
xorg-x11-fonts-Type1 7.5-3 OK
The six packages starting with "xorg-x11-fonts-" are the only six shown by the Cygwin setup executable.
I installed Antergos (easy version of Arch) with the Japanese environment.
But I wanted to chaned the language to English, so I reffer the wiki article then run some commands after uncomment #en_US.UTF-8 UTF-8 in /etc/locale.gen and edit /etc/locale.conf into following:
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
The problem starts from here.
I restarted my computer and found that gnome-terminal doesn't work.
I substituted eshell on Emacs and run gnome-terminal command, then got error messages:
(process:1202): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8
The output of locale command is following:
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=ja_JP.utf8
LC_TIME=ja_JP.utf8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=ja_JP.utf8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=ja_JP.utf8
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT=ja_JP.utf8
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
What changes some part of locale setting into Japanese? Or other reasons which terminate gnome-terminal exist?
I have tried solutions sugestted here https://bbs.archlinux.org/viewtopic.php?id=180103 .
Thank you.
I had the same problem some time ago. I fixed my locale config running this command
sudo localedef -f UTF-8 -i en_US en_US.UTF-8
The meaning of status code 8 is documented on gnome's website here:
The environment that gnome-terminal-server is started with does not
correctly set the locale to a UTF-8 locale. Consult your
distribution's documentation on how to fix this. Note that is it not
relevant to check the locale settings from a different terminal (e.g.
xterm); what counts is the environment that the session dbus-daemon
passes to the processes it starts.
So you're right, this is probably due to locale settings. I don't quite understand all the details, but if I set ~/.xinitrc to exec gnome-session and then run startx, I get a similar error to yours.
However, if instead of running startx, I start the gdm display manager (via systemctl start gdm.service on Arch), I can spawn a gnome-terminal correctly. So if you're okay with using gdm, that may be a solution. Lightdm also works, though SLiM doesn't (from my experience).
In the past, I also had to install the vte3 package for gnome-terminal to work, so make sure that's installed as well. And FWIW, sudo gnome-terminal seems to always work.
Did you think to regenerate your locales after you had edited your /etc/locale.gen file ?
locale-gen
I think in your explanation you mixed the /etc/locale.gen and the /etc/locale.conf files. Be sure you edited the correct file with the correct values.
Ok this is how I solved it;
sudo locale-gen --purge --no-archive
Then; sudo update-initramfs -u
Nothing with locale worked for me. Once changed back the default python version (3.5 on ubuntu16), terminal worked just fine.
I had eclipse installed (well, unpacked) under my home dir (~/eclipse) and it worked ok (well, as much as you can say it about eclipse). Today it went totally crazy, throwing "stack overflow" errors all the time. (BTW, did you know it is completely impossible to google for "stack overflow" problems these days? Guess what you get... :)
So I downloaded the latest version and installed it under /opt/eclipse this time. When trying to run it from my user terminal I get loads of errors:
(eclipse:28336): GLib-GObject-WARNING
**: invalid (NULL) pointer instance
(eclipse:28336): GLib-GObject-CRITICAL
**: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)'
failed
(eclipse:28336): Gtk-CRITICAL **:
gtk_settings_get_for_screen: assertion
`GDK_IS_SCREEN (screen)' failed
(eclipse:28336): Gtk-WARNING **:
Screen for GtkWindow not set; you must
always set a screen for a GtkWindow
before using the window
etc. etc.
Running it from root terminal works fine (and in fact starts much faster then the previous version).
Doing this didn't help:
xhost +localhost
xhost +<my-user>
Neither did this:
chroot -R root:root /opt/eclipse
chroot -R my-group:my-user /opt/eclipse
Any suggestions how to solve this?
EDIT: curiously, unpacking it again, this time under my home dir didn't help either. Showing that giving up does not help much...
Not sure how helpful this is, but that kind of error message happens when the DISPLAY is not set properly: https://bugs.eclipse.org/bugs/show_bug.cgi?id=314849.
If your display is set, I'm not sure where to go from here since you've already done xhost +...