What does the error "Fatal IO error 0 (Success) on X server" mean? The error is produced when an X client tries to call XvCreateImage(), and it results in the client terminating.
X.0.log shows the following version information:
X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux ori-laptop 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=UUID=df637de9-47ed-4453-9393-67e2e2ffaa2f ro quiet splas
I had the same problem, i could solve it by removing ~/.gconf/desktop/gnome/peripherals. You can move/rename the whole ~/.gconf/desktop/gnome directory just to test if it works. Then just test folder by folder which one of the configurations causes the problem.
Hope it helps.
Related
I'm trying to edit a ruby file in my spacemacs editor.
When I open the ruby file I get this debugging information:
[rbenv] Using the currently activated ruby.
evil-line-move: End of buffer
Suspicious state from syntax checker ruby: Flycheck checker ruby returned 1, but its output contained no errors: ruby: /usr/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /home/sfernandez/.rbenv/versions/2.7.0/lib/libruby.so.2.7)
Try installing a more recent version of ruby, and please open a bug report if the issue persists in the latest release. Thanks!
I've tried the solution from this post:
https://ubuntuforums.org/showthread.php?t=2375927
I tried doing this after changing directory to /usr/lib/x86_64-linux-gnu
sudo mv libcrypt.so.1 libcrypt.so.1.old
After I executed this line I was locked out from doing any commands with sudo. And received an error: sudo: account validation failure, is your account locked. I was able to get sudo access again by just refresh installing my system with Pop!_OS, I guess moving the link for libcrypt.so.1 caused something bad to happen, so won't do that again.
I'm sure this all makes sense, but I feel like I'm missing something and that this shouldn't be hard to fix. Would appreciate any guidance on this.
If it helps here's my system info with neofetch
///////////// sfernandez#pop-os
///////////////////// -----------------
///////*767//////////////// OS: Pop!_OS 20.04 LTS x86_64
//////7676767676*////////////// Host: Inspiron 7559 1.3.1
/////76767//7676767////////////// Kernel: 5.4.0-7634-generic
/////767676///*76767/////////////// Uptime: 9 mins
///////767676///76767.///7676*/////// Packages: 1763 (dpkg), 20 (flatpak)
/////////767676//76767///767676//////// Shell: bash 5.0.16
//////////76767676767////76767///////// Resolution: 1920x1080, 1920x1080
///////////76767676//////7676////////// DE: GNOME
////////////,7676,///////767/////////// WM: Mutter
/////////////*7676///////76//////////// WM Theme: Pop
///////////////7676//////////////////// Theme: Pop [GTK2/3]
///////////////7676///767//////////// Icons: Pop [GTK2/3]
//////////////////////'//////////// Terminal: gnome-terminal
//////.7676767676767676767,////// CPU: Intel i5-6300HQ (4) # 3.200GHz
/////767676767676767676767///// GPU: Intel HD Graphics 530
/////////////////////////// GPU: NVIDIA GeForce GTX 960M
///////////////////// Memory: 2328MiB / 7828MiB
/////////////
After doing some more work on this I've learned a little about symbolic links. I know that libcrypt.so.1 is a symbolic link to libcrypt.so.1.1.0 after running ls -l | grep "libcrypt.so.1" I get the following:
lrwxrwxrwx 1 root root 39 Mar 10 12:24 libcrypt.so -> /lib/x86_64-linux-gnu/libcrypt.so.1.1.0
lrwxrwxrwx 1 root root 17 Mar 10 12:24 libcrypt.so.1 -> libcrypt.so.1.1.0
-rw-r--r-- 1 root root 202760 Mar 10 12:24 libcrypt.so.1.1.0
Running ls -l after changing directory to $HOME/.rbenv/versions/2.7.0/lib I get the following output:
lrwxrwxrwx 1 sfernandez sfernandez 16 Jun 27 20:25 libruby.so -> libruby.so.2.7.0
lrwxrwxrwx 1 sfernandez sfernandez 16 Jun 27 20:25 libruby.so.2.7 -> libruby.so.2.7.0
Now, I think the problem is that libruby.so.2.7 can reference the ruby code just fine, but it also needs access to whatever is referenced by libcrypt.so.1. Anyone got any ideas?
This question is still relevant please help
I have the same issue (pop_os 20.04 LTS, spacemacs 0.300.0#27.1).
The only way I managed to make it work was downgrading emacs to version 26.3.
[UPDATE]
So after about half a year I had to set up a new laptop and was faced with the same problem. After hours of debugging I've finally found my old answer and managed to fix the problem.
Again, the solution for pop_os is to install the app from the pop!_shop that is named Emacs (Terminal).
I'm trying to install the Awesome VM in Alpine Linux following this tutorial.
I have passed the following commands:
$ sudo apk add awesome feh lxterminal
$ sudo apk add lua
$ setup-xorg-base
Then and all the commands in the "Start Your Desktop" section ...
... but when I pass this command :
$ startx
I got the following errors:
hostname: dev-box: Host not found
xauth: unable to link authority file /home/babonet13/.Xauthority, use /home/babonet13/.Xauthority-n
xauth: unable to link authority file /home/babonet13/.Xauthority, use /home/babonet13/.Xauthority-n
X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.14.39-0-vanilla x86_64 Alpine Linux
Current Operating System: Linux dev-box 4.14.69-0-vanilla #1-Alpine SMP Mon Sep 10 19:33:23 UTC 2018 x86_64
Kernel command line: BOOT_IMAGE=vmlinuz-vanilla root=UUID=26f38daa-766f-49f1-abb3-a0f7e8fc9d15 modules=sd-mod,usb-storage,ext4 nomodeset quiet rootfstype=ext4 initrd=initramfs-vanilla
Build Date: 30 August 2018 02:57:08PM
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 5 13:33:54 2018
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
deallocvt: can't open console
Can could help me to start debugging it in the right way?
This is a problem installing X.org on Alpine Linux, you have not yet reached the point where Awesome is involved. I suggest you edit your post title and tags to reflect this. Also, stackoverflow is for programming question. If you have further installation issues, it is preferred to use SuperUser
Nevertheless:
(EE) no screens found(EE)
This is the error. It usually means you didn't install the video drivers or your kernel doesn't have the right modules or you use a static X.org build and it doesn't have the right compile options or you have a custum xorg.conf[.in] file that isn't representative of your setup.
/var/log/Xorg.0.log may have more information, but from my past experience with this kind of issue, wont provide more relevant details.
Also, it is AwesomeWM, not Awesome-VM.
I'm newbie in DB2 database administration and I couldn't think that I'd be stuck with the installation process. I read some documents before installation and found an interesting "db2prereqcheck" thing.
So I tried to run it before installation and got an error:
DBT3505E The db2prereqcheck utility was unable to determine the Linux distribution level.
About this error from ibm:
IBM Knowledge Center: DBT3505E
IBM Support: db2prereqcheck fails checking Linux distribution
I found some other answers where suggest to delete the files "/etc/issue" and "/etc/issue.net".
I checked my "/etc/issue*" files according to the tips. I filled that files with the example from the article in IBM Support, but nothing has changed. I tried running this script on other servers with CentOS, Debian operating systems, but got another error:
./db2prereqcheck
DBI1189E There has been an attempt to use db2prereqcheck
on an image for a platform that does not match the current platform
'Linux/x86-64' on which it is being run.
Explanation:
Possible causes include:
- This DB2 install image is not valid for the current
platform.
- The current platform is not supported by DB2.
User Response:
Install DB2 using the DB2 install image that corresponds
with the current platform 'Linux/x86-64'.
I've already installed db2, but my self-esteem is down. So the question is: my hands are a problem or is the problem in another? And how to make db2 work
Technical details:
cat /etc/issue
Amazon Linux AMI release 2018.03
Kernel \r on an \m
cat /etc/*-rel*
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
Amazon Linux AMI release 2018.03
cpe:/o:amazon:linux:2018.03:ga
uname -a
Linux hostname.host 4.14.47-56.37.amzn1.x86_64 #1 SMP Wed Jun 6 18:49:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
As you may have noticed, this is an EC2 instance.
DB2 versions:
IBM® Db2 11.1 Developer-C Edition for Linux® on AMD64 and Intel® EM64T systems (x64)
IBM® DB2 Express-C Version 11.1
I would appreciate your help in this matter. Thank you for your time.
If db2prereqcheck reports :
DBT3505E The db2prereqcheck utility was unable to determine the Linux
distribution level. Aborting the current installation ... Run
installation with the option "-f sysreq" parameter to force the
installation.
and if other IBM suggestions do not apply, then you may be able to avoid this symptom with the following workaround:
(as root)
cp /etc/os-release /etc/lsb-release
The reason it works is that some versions of db2prereqcheck look only for the following files in turn:
/etc/centos-release
/etc/redhat-release
/etc/SuSE-release
/etc/lsb-release
If none of those files are present, the DBT3505E symptom can result.
If your distro (or container) has an equivalent file (for example, Debian may have /etc/os-release) then simply copying it to /etc/lsb-release will allow db2prereqcheck to complete.
db2prereqcheck checks and understands only /etc/SuSE-release with the following content:
SUSE Linux Enterprise Server 15 (x86_64)
VERSION = 15
PATCHLEVEL= 1
This works also with OpenSuse Leap 15.1. This file is deprecated since SLES 12. So you must create it your self. Then run db2prereqcheck and install all missing libraries and kernel sources mentioned. Having all requirements fulfilled you may finally see the segmentation fault message:
Validating "Intel TCO WatchDog Timer Driver modules" ...
DBT3546E The db2prereqcheck utility failed to determine whether the
following file or package exists: "".
Segmentation fault (core dumped)
Don't worry!
Simply retest with db2prereqcheck -i. The -i parameter checks for prerequisites that are not Db2 pureScale related. If we don't install pureScale and all requirement are fulfilled, we can ignore this ugly segmentation fault.
Otherwise you must blacklist by adding:
blacklist iTCO_wdt
blacklist iTCO_vendor_support
Into the file /etc/modprobe.d/blacklist.conf
A further issue is related to:
export DISPLAY=your.machine.ip:0.0
running ./db2setup as root doesn't work.
./db2_install is deprecated, but it works.
First create the db2 users and groups as described by the IBM Knowledge Center.
Then run ./db2_install as root, followed by creating an instance using db2icrt.
Login as db2inst1 and test as described by the IBM Knowledge Center eventually creating the SAMPLE Database, etc. Normally "first steps" would do the job, but it crashes with javascript error. Hence you must do it manually!
Additional manual configuration may be required as opening the firewall for port 50001 and setting this port within /etc/services and within dbm cfg with:
db2 update dbm cfg using SVCENAME 50001
or
db2 update dbm cfg using SVCENAME db2c_db2inst1
If you use the latter you must update /etc/services with the line:
db2c_db2inst1 50001/tcp #and a comment like db2 tcp/ip
connection port.
I cannot pass build tests when I build Golang from source:
hg clone -u release https://code.google.com/p/go
cd go/src
./all.bash
....
ok net/url 0.005s
ok os 0.595s
--- FAIL: TestExtraFiles (0.12 seconds)
exec_test.go:230: TestExtraFiles: Something already leaked - closed fd 3
exec_test.go:403: Run: exit status 1; stdout "leaked parent file. fd = 10; want 9\n", stderr ""
FAIL
FAIL os/exec 0.822s
ok os/signal 0.511s
please help. this is on my webfaction shared machine.
[~] lsb_release -a
LSB Version: :core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 5.10 (Final)
Release: 5.10
Codename: Final
It's a bug in CentOS 5/RHEL 5 according to issue 3001, basicly the kernel ignores O_CLOEXEC.
So either ignore the error (bad idea) or move to a more recent Linux version.
I'm getting the following error on a Darwin machine:
awk: cannot execute [Interrupted system call]
This is the OS version:
Darwin ...... 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01
PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC Power Macintosh
Do you know what it might be?
The error message is giving you a clue. Somewhere a system call is being made by awk which is not working and the calling script is consequently being "interrupted". You'll need to narrow down the scope of the question by finding which cron scripts are failing with this error. Use grep to look through your cron scripts for suspects.
From the information you've provided I'd guess that a script that uses awk is making a system call (the code will be system(some_shell_cmd) ) to a utility that doesn't exist; is installed in an unusual location; is not on your $PATH; is not executable; or is itself a perl, python, or sh ($SHELL) script for which the interpreter has either not been installed or is not functioning properly.