The x11 connection broke error 1 did the x11 server die astra linux

SystemD не сумел выключить машину

Отвалился usb-hub с флешкой воткнутой, и не захотел реиницилизироваться.
Восьмое чувство подсказало, что не стоит удалённо перезагружать машину.

Внезапно, оказалось что я угадал, и systemd был не готов к серверному юзкейсу: https://i.imgur.com/xTBtiVJ.jpg

systemd зомбанул машину: потушил все сервисы, и не выключил.

Лог отключения до последней записи:

Почему-то хардварный watchdog тоже не сработал.
Нужно будет разбираться, почему. Он должен был спасти.

P.S. система не зависла, перезагрузил с помощью magic keys.

Отвалился usb-hub с флешкой воткнутой В проблемах с железом виноват systemd

_Все «хардварные» вотчдоги — глюкло.

_Все «хардварные» вотчдоги — глюкло.

Возможно я чего-то не так настроил. Нужно будет провести учения по ГО.

Feb 12 08:10:52 optiplex systemd[1]: Failed to attach 26217 to compat systemd cgroup /system.slice/virtualbox.service: No such file or directory

У тебя в системе какой-то ад происходит.

В дебиане всегда так? С каждым разом всё больше убеждаюсь, что дебиан — это такая сложная система уравновешивающих друг друга дичайших костылей и подпорок, от которой хочется плакать кровавыми слезами.

Ватчдог без DefaultDependencies=no , ахаха, что ты делаешь, прекрати.

У тебя в системе какой-то ад происходит. В дебиане всегда так? С каждым разом всё больше убеждаюсь, что дебиан — это такая сложная система уравновешивающих друг друга дичайших костылей и подпорок, от которой хочется плакать кровавыми слезами.

Ну, мы на эту тему уже говорили. Повторюсь: ты, как саппорт, фокусируешься на том, что конечные юзеры дебилы. Не так сконфигурировали, не так дышат и не в ту сторону молятся. Узко говоря, фактически ты прав.

Я как конечный пользователь, констатирую, что эта фигня ломается уже третий раз за полгода. Если гуру-дистростроители не могут совладать, юзер с 10+ летним стажем не может совладать, то домохозяйкам то как жить? Есть ли конечному пользователю разница, по чьей вине нужно раз в два месяца разгребать проблемы? Ладно бы ещё я ковырялся, так нет же ж. Просто хочу как домохозяйка: вкл/выкл.

По вочдогу, я так и подозреваю, что он либо вообще не был запущен, либо не был остановлен. А железо скорее всего не виновато.

В дебиане всегда так? С каждым разом всё больше убеждаюсь, что дебиан — это такая сложная система уравновешивающих друг друга дичайших костылей и подпорок, от которой хочется плакать кровавыми слезами.

Из бесплатного для сервера выбора особо и нет. Либо Debian с Ubuntu, либо CentOS. И все они сборище костылей различной конфигурации.

Источник

The x11 connection broke error 1 did the x11 server die astra linux

I’m working on migrating an application from Qt 5.9 to Qt 5.14. For 64-bit Linux we usually run the application with X11 forwarding enabled so we can use the application from a Windows workstation.

This approach works fine when using the version of the application built with Qt 5.9. But with Qt 5.14, I see a quick flash, like the application is trying to start, and then nothing. An error message says «The X11 connection broke (error 1). Did the X11 server die?». The server hasn’t died, but the connection did break. I’ve seen this with two SSH clients on my workstation. I’ve tried upgrading the X11 software on the Linux environment, but that hasn’t worked. The X11 software on my Windows workstation is Xming 6.9.0.31.

A colleague tried executing the application built with Qt 5.14 using a Linux environment with a direct connected console, and this worked without problems. So something related to X11 seems to be the issue. Have any problems like this been seen with Qt 5.14?

The public release Xming server doesn’t seem to be actively supported and was developed way back int the XP days. I’d suggest that the windoze X server itself is less than stable.

Try it with the cygwin X server before making additional asusmptions.

Are you starting your application from a terminal ?
If so, you should start it with the QT_DEBUG_PLUGINS environment variable set to 1 to see if there’s some information with regard to the xcb plugin.

The public release Xming server doesn’t seem to be actively supported and was developed way back int the XP days. I’d suggest that the windoze X server itself is less than stable.

Try it with the cygwin X server before making additional asusmptions.

@SGaist I’m seeing messages like this when that environment variable is set to 1 and Qt 5.14 is used:

With Qt 5.9 there is much less output, but I see messages like these:

With Qt 5.9 the application does start.

@Kent-Dorfman xming is not outdated, it’s just no longer free http://www.straightrunning.com/XmingNotes/ but actively developed. It’s just OP using very outdated one.

@Kent-Dorfman I tried my test using Cygwin’s X server instead of the free Xming software. It worked.

@artwaw
**
@Kent-Dorfman xming is not outdated, it’s just no longer free http://www.straightrunning.com/XmingNotes/ but actively developed. It’s just OP using very outdated one.
ed text**

The «free version» the op uses is outdated. hasn’t been updated in like 6 or 7 years.

Источник

The X11 connection broke (error 1). Did the X11 server die? #466

Hey, I’m currently using splash via Docker and I’m having my container «randomly» die with an exit code of 137. The only relevant message I can see in the log output is the last line:

I’ve also seen this in the dimes output but I think it might be a separate condition:

I’d say this happens after I have crawled a couple of hundred pages (it doesn’t seem to be anything specific about an individual page because it crashes randomly). Possibly something running out of memory? Curious if others have seen the same issue or have ideas how I might get more information to help debug.

The text was updated successfully, but these errors were encountered:

Did you figure this out? I have the same problem (but not with splash) on Circleci but not on Virtualbox 🙁

Hey @kevinsimper. I unfortunately never made it anywhere in terms of actually fixing the issue. I’m running with Docker so I just set the thing to restart on error . which is ugly but has been working for my use case. Not sure if it is a version or resource issue.

Anyone find a resolution to this?

@nmilford It is not an easy problem, but I solved it in my case by installing a couple of other things. You can see it here. It is probably not related https://github.com/kevinsimper/wkhtmltoimage-docker

This may just be coincidence and may not apply to everyone else’s crashing but I noticed that Docker started crashing when I added the following and stopped crashing when I removed it.

When it crashed, the output was:

I think this problem is related to memory.
I had the same problem on VPS with 512 MB RAM but it never happened again on VPS with over 1024 MB RAM.

use splash with scrapy ,the same error
but i change docker ram to 4G, crash is still

I am getting this error too. I am running splash with Docker and HAProxy. I do notice that after I get this, Splash instance gets restarted sometimes (by Docker I assume) and other times it just stalls. Were any of you able to figure out the root cause? Thank you.

I got the same error on another project, and the issue be gone after I remove an extra «plt.ion()»
hope it could be a hint for u.

This is an old topic, I think is related with this part of the documentation,
specially the —restart=always since looks that for production is assumed that will eventually
crash because of an increassed memory usage.

I have exactly the same problem. I solved it by allowing docker to restart always:

docker run -p 8050:8050 —memory=4.5G —restart=always scrapinghub/splash —maxrss 4000

I think this problem is related to memory.
I had the same problem on VPS with 512 MB RAM but it never happened again on VPS with over 1024 MB RAM.

but my host mem is 16G =.=.it also happend

We have run into a very similar, if not exactly the same issue. It seems, that at least in our case, it is definitely
connected to a shortage of memory, when kernel’s oom-killer starts to kill processes before docker memory limitation
or built-in splash memory limitation kicks-in.

We run splash cluster behind HAProxy and on one of the nodes (with only 2GB RAM) both running splash docker containers
suddenly stopped working correctly. Containers were still running, but splash processes were not responding.

One of them had error messages in docker logs (as the last line):
The X11 connection broke (error 1). Did the X11 server die?
Second container had no error messages in docker logs output, but log stopped in a similar time.

From kern.log it was visible, that node was under big memory pressure and oom killer killed Xvfb process (X-11 process which runs under splash container) and after some time splash process in a second container runs into a segfault (We use Ubuntu 18.04):

We started this container with recommended memory limitation flags, but limitation values were apparently too high for this node:
docker run -p 8050:8050 —memory=2.5G —restart=always scrapinghub/splash —maxrss 2000

So this limitations had not been triggered, splash processes or splash containers hadn’t been restarted and subsequently got broken or partially killed by oom-killer.

Источник

VLC. Ошибка — VLC не может декодировать формат «h264» (H264 — MPEG-4 AVC (part 10))

Ocean

New member

Имеется свежеустановленный Astra Linux Orel.

VLC не проигрывает файл mkv с кодеком H.264 (V_MPEG4/ISO/AVC по данным утилиты Mediainfo).

VLC под Windows и Ubuntu проигрывает без проблем.

При попытке проиграть в GUI пишет ниже следующее:

Ocean

New member

Разобрался в чём проблема.

В Astra Orel 2.12 используется репозиторий со старым софтом (от Debian 9).

Для корректного проигрывания MPEG4/H.264 (в моём случае) нужно использовать библиотеки libvaformat58, а в Astra Orel 2.12 версия 57.

В версии Astra Orel 2.13 уже используется репозиторий от Debian 10 и там нужная версия библиотек и всё корректно проигрывается, но 2.13 это пока эксперементальная версия и думаю в продакшен её не стоит.

Montfer

New member

Ocean

New member

При попытки использовать репозиторий от Debian 10 необходимо установить кучу зависимостей и к чему это приведёт в будущем непонятно. также появляются ошибки типа «E: Невозможно исправить ошибки, у вас отложены (held) битые пакеты.»

Пока для себя решил вопрос установкой snap пакета VLC. Тормозно, избыточно но работает.

Печально, что в Астре такой древний софт. но другой дистр использовать не могу.

Montfer

New member

При попытки использовать репозиторий от Debian 10 необходимо установить кучу зависимостей и к чему это приведёт в будущем непонятно. также появляются ошибки типа «E: Невозможно исправить ошибки, у вас отложены (held) битые пакеты.»

Пока для себя решил вопрос установкой snap пакета VLC. Тормозно, избыточно но работает.

Печально, что в Астре такой древний софт. но другой дистр использовать не могу.

Ocean

New member

Да, попробовал на свежеустановленном Орле. Тоже смог поставить libavformat58 но VLC всё равно подхватывает версию 57.

Поставил весь VLC из репозитория Debian 10. Вроде всё Ок, видео начинает проигрывать, но Атсра постоянно вываливается в окно авторизации с запросом логина и пароля.

Например открываю «Мой компьютер» или пытаюсь просмотреть видео, рабочий стол закрывается и открывается окно авторизации с запросом логина и пароля.

Или Астра глючит на VMware или новая VLC при установке сломала какие-то библиотеки.

Проверю на реальном компьютере, а не виртуальном. Спасибо за подсказки!

Источник

The X11 connection broke: I/O error (code 1) #40

I got the following error with osrf/ros:kinetic-desktop-full docker image in Fedora 24.

The gui program cannot work in this docker image.
Any help will be appreciated!

The text was updated successfully, but these errors were encountered:

Just tested the latest osrf/ros:kinetic-desktop-full image on ubuntu 16.04 (I don’t have a Fedora install), and GUI’s using X11 are working for me via the simple method way show here: http://wiki.ros.org/docker/Tutorials/GUI

Is your default display number different than :0 in Fedora? Is Fedora still using X server, not Wayland?
https://ask.fedoraproject.org/en/question/90679/cannot-start-x-server-on-f24/

The osrf/ros:kinetic-desktop-full image works well on Ubuntu 16.04, but not the Fedora 24. The Fedora 24 still using X server and my display number is :0 .

But the osrf/ros:indigo-desktop-full images works well on Fedora 24.

Is this the limitation of docker ? Something limit the docker app running on any Linux distribution?

Not sure how this would be docker specific issue if it works for one docker image but not another. I’d suspect it to be more of a Ubuntu:Xenial/Fedora-24 image/host related issue as Ubuntu:Trusty/Fedora-24 seem to be working.

Could you verify this is the case by checking if say: the gedit GUI works from Xenial docker image running on a Fedora 24 host?

I got the following error run gedit with ubuntu:16.04 docker image on Fedora 24 host

The gedit cannot work.

I used the following command to run the docker image,

Hmmm, not sure where Mir is coming into this. Are new images of Ubuntu 16:04 now using Mir by default?
I had thought that display transition would’ve been made after this LTS.

Yeah, the Ubuntu 16.04 use Mir as default display server, so the X applications in docker container can’t find the Mir server in Fedora which still use X server.

This is the drawback of docker to run GUI application in docker container. At this aspect, docker container is not better than virtual machine.

Well, that’s the cost of adopting different display technologies; the diversity pushes innovation and security at the cost of convenience and uniformity. Still, I kind of wish Canonical had adopted Wayland instead.
A good discussion on the topic from 6 months ago:
https://www.reddit.com/r/linux/comments/4bq9kl/eli5_wayland_vs_mir_vs_x11/

Perhaps you could follow online guides to install Wayland packages onto the Ubuntu image, and then mount the necessary components for Wayland to forward the GUI in the container to the host display. No one has yet contributed to that section of the ros docker wiki, and I’d hazard a guess many more folks like you may find it useful in the coming future as Xserver dies a slow death.

Источник

We have run into a very similar, if not exactly the same issue. It seems, that at least in our case, it is definitely
connected to a shortage of memory, when kernel’s oom-killer starts to kill processes before docker memory limitation
or built-in splash memory limitation kicks-in.

We run splash cluster behind HAProxy and on one of the nodes (with only 2GB RAM) both running splash docker containers
suddenly stopped working correctly. Containers were still running, but splash processes were not responding.

One of them had error messages in docker logs (as the last line):
The X11 connection broke (error 1). Did the X11 server die?
Second container had no error messages in docker logs output, but log stopped in a similar time.

From kern.log it was visible, that node was under big memory pressure and oom killer killed Xvfb process (X-11 process which runs under splash container) and after some time splash process in a second container runs into a segfault (We use Ubuntu 18.04):

Oct  5 21:59:27 splash3 kernel: [31703.824027] [ 2227]     0  2227     1824       83       9       3        0             0 uniq
Oct  5 21:59:27 splash3 kernel: [31703.824030] [ 2228]     0  2228     6187      122      17       3        0             0 awk
Oct  5 21:59:27 splash3 kernel: [31703.824032] Out of memory: Kill process 2005 (python3) score 486 or sacrifice child
Oct  5 21:59:27 splash3 kernel: [31703.824239] Killed process 2248 (Xvfb) total-vm:189892kB, anon-rss:160kB, file-rss:0kB
Oct  5 22:48:07 splash3 kernel: [34623.719612] python3[2007]: segfault at bbadbeef ip 00007f6835cc07dd sp 00007ffc02535300 error 6 in libQt5WebKit.so.5.212.0[7f6833968000+2db0000]

We started this container with recommended memory limitation flags, but limitation values were apparently too high for this node:
docker run -p 8050:8050 --memory=2.5G --restart=always scrapinghub/splash --maxrss 2000

So this limitations had not been triggered, splash processes or splash containers hadn’t been restarted and subsequently got broken or partially killed by oom-killer.

SystemD не сумел выключить машину

Отвалился usb-hub с флешкой воткнутой, и не захотел реиницилизироваться.
Восьмое чувство подсказало, что не стоит удалённо перезагружать машину.

Внезапно, оказалось что я угадал, и systemd был не готов к серверному юзкейсу: https://i.imgur.com/xTBtiVJ.jpg

systemd зомбанул машину: потушил все сервисы, и не выключил.

Лог отключения до последней записи:

Почему-то хардварный watchdog тоже не сработал.
Нужно будет разбираться, почему. Он должен был спасти.

P.S. система не зависла, перезагрузил с помощью magic keys.

Отвалился usb-hub с флешкой воткнутой В проблемах с железом виноват systemd

_Все «хардварные» вотчдоги — глюкло.

_Все «хардварные» вотчдоги — глюкло.

Возможно я чего-то не так настроил. Нужно будет провести учения по ГО.

Feb 12 08:10:52 optiplex systemd[1]: Failed to attach 26217 to compat systemd cgroup /system.slice/virtualbox.service: No such file or directory

У тебя в системе какой-то ад происходит.

В дебиане всегда так? С каждым разом всё больше убеждаюсь, что дебиан — это такая сложная система уравновешивающих друг друга дичайших костылей и подпорок, от которой хочется плакать кровавыми слезами.

Ватчдог без DefaultDependencies=no , ахаха, что ты делаешь, прекрати.

У тебя в системе какой-то ад происходит. В дебиане всегда так? С каждым разом всё больше убеждаюсь, что дебиан — это такая сложная система уравновешивающих друг друга дичайших костылей и подпорок, от которой хочется плакать кровавыми слезами.

Ну, мы на эту тему уже говорили. Повторюсь: ты, как саппорт, фокусируешься на том, что конечные юзеры дебилы. Не так сконфигурировали, не так дышат и не в ту сторону молятся. Узко говоря, фактически ты прав.

Я как конечный пользователь, констатирую, что эта фигня ломается уже третий раз за полгода. Если гуру-дистростроители не могут совладать, юзер с 10+ летним стажем не может совладать, то домохозяйкам то как жить? Есть ли конечному пользователю разница, по чьей вине нужно раз в два месяца разгребать проблемы? Ладно бы ещё я ковырялся, так нет же ж. Просто хочу как домохозяйка: вкл/выкл.

По вочдогу, я так и подозреваю, что он либо вообще не был запущен, либо не был остановлен. А железо скорее всего не виновато.

В дебиане всегда так? С каждым разом всё больше убеждаюсь, что дебиан — это такая сложная система уравновешивающих друг друга дичайших костылей и подпорок, от которой хочется плакать кровавыми слезами.

Из бесплатного для сервера выбора особо и нет. Либо Debian с Ubuntu, либо CentOS. И все они сборище костылей различной конфигурации.

Источник

The X11 connection broke: I/O error (code 1) #40

I got the following error with osrf/ros:kinetic-desktop-full docker image in Fedora 24.

The gui program cannot work in this docker image.
Any help will be appreciated!

The text was updated successfully, but these errors were encountered:

Just tested the latest osrf/ros:kinetic-desktop-full image on ubuntu 16.04 (I don’t have a Fedora install), and GUI’s using X11 are working for me via the simple method way show here: http://wiki.ros.org/docker/Tutorials/GUI

Is your default display number different than :0 in Fedora? Is Fedora still using X server, not Wayland?
https://ask.fedoraproject.org/en/question/90679/cannot-start-x-server-on-f24/

The osrf/ros:kinetic-desktop-full image works well on Ubuntu 16.04, but not the Fedora 24. The Fedora 24 still using X server and my display number is :0 .

But the osrf/ros:indigo-desktop-full images works well on Fedora 24.

Is this the limitation of docker ? Something limit the docker app running on any Linux distribution?

Not sure how this would be docker specific issue if it works for one docker image but not another. I’d suspect it to be more of a Ubuntu:Xenial/Fedora-24 image/host related issue as Ubuntu:Trusty/Fedora-24 seem to be working.

Could you verify this is the case by checking if say: the gedit GUI works from Xenial docker image running on a Fedora 24 host?

I got the following error run gedit with ubuntu:16.04 docker image on Fedora 24 host

The gedit cannot work.

I used the following command to run the docker image,

Hmmm, not sure where Mir is coming into this. Are new images of Ubuntu 16:04 now using Mir by default?
I had thought that display transition would’ve been made after this LTS.

Yeah, the Ubuntu 16.04 use Mir as default display server, so the X applications in docker container can’t find the Mir server in Fedora which still use X server.

This is the drawback of docker to run GUI application in docker container. At this aspect, docker container is not better than virtual machine.

Well, that’s the cost of adopting different display technologies; the diversity pushes innovation and security at the cost of convenience and uniformity. Still, I kind of wish Canonical had adopted Wayland instead.
A good discussion on the topic from 6 months ago:
https://www.reddit.com/r/linux/comments/4bq9kl/eli5_wayland_vs_mir_vs_x11/

Perhaps you could follow online guides to install Wayland packages onto the Ubuntu image, and then mount the necessary components for Wayland to forward the GUI in the container to the host display. No one has yet contributed to that section of the ros docker wiki, and I’d hazard a guess many more folks like you may find it useful in the coming future as Xserver dies a slow death.

Yeah, the Ubuntu 16.04 use Mir as default display server

Sorry for arriving late to the thread. I’m interesting in this affirmation, could you please point to the information source that explain that 16.04 is using Mir by default?

AFAIK, it won’t be the default manager even for the 16.10 version.

Источник

The X11 connection broke (error 1). Did the X11 server die? #466

Hey, I’m currently using splash via Docker and I’m having my container «randomly» die with an exit code of 137. The only relevant message I can see in the log output is the last line:

I’ve also seen this in the dimes output but I think it might be a separate condition:

I’d say this happens after I have crawled a couple of hundred pages (it doesn’t seem to be anything specific about an individual page because it crashes randomly). Possibly something running out of memory? Curious if others have seen the same issue or have ideas how I might get more information to help debug.

The text was updated successfully, but these errors were encountered:

Did you figure this out? I have the same problem (but not with splash) on Circleci but not on Virtualbox 🙁

Hey @kevinsimper. I unfortunately never made it anywhere in terms of actually fixing the issue. I’m running with Docker so I just set the thing to restart on error . which is ugly but has been working for my use case. Not sure if it is a version or resource issue.

Anyone find a resolution to this?

@nmilford It is not an easy problem, but I solved it in my case by installing a couple of other things. You can see it here. It is probably not related https://github.com/kevinsimper/wkhtmltoimage-docker

This may just be coincidence and may not apply to everyone else’s crashing but I noticed that Docker started crashing when I added the following and stopped crashing when I removed it.

When it crashed, the output was:

I think this problem is related to memory.
I had the same problem on VPS with 512 MB RAM but it never happened again on VPS with over 1024 MB RAM.

use splash with scrapy ,the same error
but i change docker ram to 4G, crash is still

I am getting this error too. I am running splash with Docker and HAProxy. I do notice that after I get this, Splash instance gets restarted sometimes (by Docker I assume) and other times it just stalls. Were any of you able to figure out the root cause? Thank you.

I got the same error on another project, and the issue be gone after I remove an extra «plt.ion()»
hope it could be a hint for u.

This is an old topic, I think is related with this part of the documentation,
specially the —restart=always since looks that for production is assumed that will eventually
crash because of an increassed memory usage.

I have exactly the same problem. I solved it by allowing docker to restart always:

docker run -p 8050:8050 —memory=4.5G —restart=always scrapinghub/splash —maxrss 4000

I think this problem is related to memory.
I had the same problem on VPS with 512 MB RAM but it never happened again on VPS with over 1024 MB RAM.

but my host mem is 16G =.=.it also happend

We have run into a very similar, if not exactly the same issue. It seems, that at least in our case, it is definitely
connected to a shortage of memory, when kernel’s oom-killer starts to kill processes before docker memory limitation
or built-in splash memory limitation kicks-in.

We run splash cluster behind HAProxy and on one of the nodes (with only 2GB RAM) both running splash docker containers
suddenly stopped working correctly. Containers were still running, but splash processes were not responding.

One of them had error messages in docker logs (as the last line):
The X11 connection broke (error 1). Did the X11 server die?
Second container had no error messages in docker logs output, but log stopped in a similar time.

From kern.log it was visible, that node was under big memory pressure and oom killer killed Xvfb process (X-11 process which runs under splash container) and after some time splash process in a second container runs into a segfault (We use Ubuntu 18.04):

We started this container with recommended memory limitation flags, but limitation values were apparently too high for this node:
docker run -p 8050:8050 —memory=2.5G —restart=always scrapinghub/splash —maxrss 2000

So this limitations had not been triggered, splash processes or splash containers hadn’t been restarted and subsequently got broken or partially killed by oom-killer.

Источник

Linux X11 Connection Rejected Because of Wrong Authentication Error and Solution

Q. I’m trying to login to my remote Ubuntu Linux server from Mac OS X desktop using following command:
ssh -X user@vpn.officeserver.example.com xeyes

But I’m getting an error that read as follows:

X11 connection rejected because of wrong authentication.

• No ads and tracking
• In-depth guides for developers and sysadmins at Opensourceflare✨
• Join my Patreon to support independent content creators and start reading latest guides:
  • How to set up Redis sentinel cluster on Ubuntu or Debian Linux
  • How To Set Up SSH Keys With YubiKey as two-factor authentication (U2F/FIDO2)
  • How to set up Mariadb Galera cluster on Ubuntu or Debian Linux
  • A podman tutorial for beginners – part I (run Linux containers without Docker and in daemonless mode)
  • How to protect Linux against rogue USB devices using USBGuard

Join Patreon ➔

How do I fix this error?

A. This error can be caused by various factors. Try following solutions:

Make sure you are not running out of disk space

Run df and make sure you have sufficient disk space:
$ df -H
If you are low on disk space remove unnecessary files from your system.

Make sure

/.Xauthority owned by you

Run following command to find ownweship:
$ ls -l

/.Xauthority
Run chown and chmod to fix permission problems
$ chown user:group

/.Xauthority
$ chmod 0600

/.Xauthority
Replace user:group with your actual username and groupname.

Make sure X11 SSHD Forwarding Enabled

Make sure following line exists in sshd_config file:
$ grep X11Forwarding /etc/ssh/sshd_config
Sample output:

If X11 disabled add following line to sshd_cofing and restart ssh server:
X11Forwarding yes

Make sure X11 client forwarding enabled

Make sure your local ssh_config has following lines:
Host *
ForwardX11 yes

Finally, login to remote server and run X11 as follows from your Mac OS X or Linux desktop system:
ssh -X user@remote.box.example.com xeyes

🐧 Get the latest tutorials on Linux, Open Source & DevOps via

Comments on this entry are closed.

In the end of the post you wrote “Finally, login to remote server and run X11 as follows from your Mac OS X or Linux desktop system”. What about Microsoft Windows Os’s? How do i use X11Forwarding in Windows?

Use Putty Windows ssh client, it has support for X11 forwarding. You also need to install Win32-X11 for local display.

There is a programm – Xming, – that allows run some application from Linux server at Windows desktop.
“Xming may be used with implementations of SSH to securely forward X11 sessions from Unix machines. It supports PuTTY and ssh.exe, and comes with a version of PuTTY’s plink.exe.”
http://en.wikipedia.org/wiki/Xming

Vivek, I believe since Mac OS X 10.4, you must use the -Y flag (instead of -X) to enable X11 forwarding. If I use -X on 10.4 or 10.5, I get the authentication error, but -Y always works.

Not sure why Apple broke convention here, but I think this is the fix you are looking for.

leamanc: For weeks I was getting authentication errors when I SSH-connected using -X. I tried out many things I found on other blogs but none worked out for me. Many thanks! Using -Y fixed it.

Another issue might be a rc file named either

/.ssh/rc or /etc/ssh/sshrc. If one of these files is present, it has to handle (given) xauth parameters as well, since sshd won’t execute xauth by itself anymore.

Jockie, thank u.
I did have a rc in my

I had a problem : when I tried to run a Xorg program, it returned :
—–
ego@Darth-Vader

% xcalc
X11 connection rejected because of wrong authentication.
Error: Can’t open display: localhost:10.0
—–

I fixed the problem by add -Y function in my ssh command :
—–
ssh -X -Y user@host
—–

(I’m sorry if my language isn’t clear, I’m not very good in english :/ )

The -X flag works again, on Mac OS X. I am running version 10.6.4

I don’t know if it ever wasn’t working, for sure. But it is working now. There should be no reason to use the -Y flag (IMHO). It certainly shouldn’t be your first choice, as the -Y flag enables “trusted” forwarding, which are NOT subjected to the X11 SECURITY extension controls. This could leave your session vulnerable to keystroke monitoring.

Fly safe – Metajunkie

The fix was to add
—
X11UseLocalhost yes
—
to your /etc/ssh/sshd.config

This did the trick for me – at least.

This did the trick!

Do this from the machine that you are ssh from:

$ xauth list $DISPLAY

You’ll get something like
machine1:10 mit-magic-cookie-1 4d22408a71a55b41ccd1657d377923ae

Now ssh to the other machine (machine2) and tell it what the cookie is by adding it to the authentication list.

$ xauth add :10 MIT-MAGIC-COOKIE-1 4d22408a71a55b41ccd1657d377923ae

The echo command should show machine1

Thanks for this!

Of course I skipped the “Check your drive space” line believing I had lots of space, and went through and checked everything else first, before running a df and seeing that, in fact, I HAD run out of space.

Clearing out an out of control log file fixed the issue in a jiffy.

Another possibility – if you ssh and immediately see an error about the .Xauthority file (unreadable, not writeable, etc.), try this:
rm .Xauthority
…logout, log back in and then all is well!

Followed your instructions and it worked for me at last. Have been trying to iplement this for the 2 weeks.

Thank you for providing such useful articles!! The very first check (df) helped me find and fix my problem. Cheers! Aleksey

In my case X11 forwarding always worked. I had no problems until today (even 2 days ago it was working:/). So I followed your instructions. Permissions X11Forwarding was disabled for some reason. I fixed both ssh_config and sshd_config. Also sshd_config already had X11UseLocahost enabled so I don’t know what’s left to check :s my account owns .Xauthority and everything you mention is fine. The application I am trying to run on Xserver via ssh is gedit and I’m getting the same error even after the changes i made.

error message:
“X11 connection rejected because of wrong authentication.
The application ‘gedit’ lost its connection to the display localhost:13.0;
most likely the X server was shut down or you killed/destroyed
the application.”

does anyone have any other ideas on this?

I ran into this same error message trying to ssh -f -Y into a Fedora 14 box using Cygwin. Turns out, after trying all of the solution suggestions above and others found elsewhere, that the problem was the Firewall/Selinux settings on the Fedora box. As they’re local I just disabled both services and now my XWin works super charm.

None of the solutions above worked for me, but I was able to create my own tunnel to bypass the built-in ssh X forwarding. This worked like a charm.

From localmachine:
ssh -R 6007:localhost:6000 remotemachine
This creates a port-forward that maps requests to port 6007 on remotemachine to port 6000 on localmachine. The default X server port (:0.0) is shorthand for 6000.

Then on the hostmachine:
export DISPLAY=localhost:7.0
This maps all display requests to port 6007 on the remotemachine

Instead of typing this every time, this can be automated by adding entries to files in

/.ssh/config
Host remotemachine
RemoteForward 6007 localhost:6000

@Metajunkie Your understanding of -X and -Y options seems to be exactly opposite of what ssh man page says. If you read the documentation on -X, it says it IS vulnerable to keystroke monitoring, and recommends using -Y option. Per document -Y should be more secure than -X.

Also, from another forum, I solved my issue by adding XAUTHORITY=

/.Xauthority environment variable, so this worked: “XAUTHORITY=

/.Xauthority DISPLAY=localhost:10.0 gnome-terminal” while this: “DISPLAY=localhost:10.0 gnome-terminal” got me an error that the display couldn’t be opened on the client with the server side giving the error ” X11 connection rejected because of wrong authentication.”. I hope this information is helpful for someone.

Thank you! I’d ran out of disc space! I can’t believe the answer was this simple! Thanks again.

“In the end of the post you wrote “Finally, login to remote server and run X11 as follows from your Mac OS X or Linux desktop system”. What about Microsoft Windows Os’s? How do i use X11Forwarding in Windows?”

Please ask ‘god knows’ questions to Bill Gates.

Thank you very much! Finally got it working with your help.

I can ssh to my new RHEL6 server from my Ubuntu 11.04 desktop OK and run X apps in my local display.

But I also have sudo privs, and for a lot of server management I need to be able to run some X apps (eg Emacs) as root. I do this on a lot of other servers running RHEL <4|5>by becoming root, exiting, and running the app, thereby using the sticky-time of the X authentication, eg

$ sudo su –
[my password]
# exit
$ sudo system-config-printer &
$

This doesn’t work on the new machine: I get
X11 connection rejected because of wrong authentication.

I can’t see what I need to change: X11 forwarding is set, and all of the above suggestions.

+1 for Eric Garcia. Thank you so much, for some reason -X or -Y were not sorting out the ports. This forced the issue and kept it secure. Thanks!

X11 forwarding over SSH had always worked for me, but I just got this error today when trying to open a file in gedit. Turns out I had a gedit instance open at the physical terminal (display 0). When I closed the locally running instance, I was able to launch a remote instance with no problem. Strange.

It is also worth noting that if you change your HOME environment available then X wont be able to find your

/.Xauthority also resulting in error “X11 connection rejected because of wrong authentication”.

I have changed my home directory using “export HOME=/other/home/directory” and forgot to link Xauthority to the new home directory. spoonyfork’s reply helped me figure it out. Thanks,

Well, I deleted .Xauthority and the system just reinstalled it with the correct permissions – hence working perfectly now.

I Love this format – thanks for the excellent solution explanation

Solved my problem… thanks!

I had the same problem, but with a small difference. User root was able to create X11 sessions without a problem, but application user got an error message when running X applications:

[wasadm@localhost eclipse]$ xclock
X11 connection rejected because of wrong authentication.
Error: Can’t open display: localhost:10.0

DISPLAY variable was set,

/.Xauthority file was owned by user, permissions was correctly set.

Solution:
Run: xauth list as root

]# xauth list
localhost/unix:13 MIT-MAGIC-COOKIE-1 c77169a6fa8139ea36f538e1c72e1b98

Add all the listed sessions to the users auth:
[wasadm@localhost

]$ xauth
Using authority file /home/wasadm/.Xauthority
xauth> add localhost/unix:13 MIT-MAGIC-COOKIE-1 c77169a6fa8139ea36f538e1c72e1b98

Hope it will help others to avoid a half day agony! 🙂

]# xhost +
access control disabled, clients can connect from any host
[root@seshu1

]# ssh -Y seshu2
root@seshu2’s password:
Last login: Tue Feb 18 12:42:19 2014
[root@seshu2

]# su – oracle
[oracle@seshu2

]$ cd /u01/app/oracle/product/11.2.0/db_home/network/admin/
[oracle@seshu2 admin]$ ls
samples shrept.lst
[oracle@seshu2 admin]$ netca

Oracle Net Services Configuration:
X11 connection rejected because of wrong authentication.
X connection to localhost:10.0 broken (explicit kill or server shutdown).

how can i solve plz telme

i am working on red hat enterprise linux

The solution is to make your server record your session detaills and then reuse them when you have become root.

1. Add this to your .bashrc:

LIVE=`echo $DISPLAY | awk -F: ‘’ | awk -F. ‘’`
xauth list | grep unix:$LIVE | awk ‘’ >xuser

2. Then when you become root (or another user)

This gives the xauth magic cookies to the current shell. It’s probably horribly insecure.

There’s also one simple detail, but alas, I did make the dumb mistake once:

Make sure that you are not sudoed into the superuser (root) account, even if you are trying to start an administration GUI tool. If sshd is properly configured it should be blocking authentication as root user, therefore the X11 connection gets denied on the remote host. When you try to start the graphical utility make sure you do so with a regular user. Don’t worry about privileges, the X11 server will present you with a dialog to enter the password to elevate privileges if necessary.

For those of you having this issue on RED HAD systems (centos, fedora etc) You have to disable SELINUX. This was preventing the .Xauthority file from creating properly. I’m sure there is a way to allow it in SELINUX, but the quick way is to disable SELINUX.

Источник

Hi

Today I had two issues.

On the first issue my PC hanged without any log at journalctl. I needed to reset it.

On the second issue it exited from OpenBox with some similar messages in the console:

The X11 connection broke (error 1). Did the X11 server die?
...
Gdk-Message: 19:56:03.700: /usr/lib/firefox: Fatal IO error 11 (Recurso no disponible temporalmente) on X server :0.
...
X connection to :0 broken (explicit kill or server shutdown).
xinit: connection to X server lost
...

This is the error on journalctl:

dic 29 19:56:03 mypc systemd-coredump[4782]: Process 567 (Xorg) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 567:
                                                  #0  0x00007f1967673615 raise (libc.so.6 + 0x3d615)
                                                  #1  0x00007f196765c862 abort (libc.so.6 + 0x26862)
                                                  #2  0x000055e75a6566ea OsAbort (Xorg + 0x14a6ea)
                                                  #3  0x000055e75a6581b1 FatalError (Xorg + 0x14c1b1)
                                                  #4  0x000055e75a65de09 n/a (Xorg + 0x151e09)
                                                  #5  0x00007f19676736a0 __restore_rt (libc.so.6 + 0x3d6a0)
                                                  #6  0x00007f1967673615 raise (libc.so.6 + 0x3d615)
                                                  #7  0x00007f196765c862 abort (libc.so.6 + 0x26862)
                                                  #8  0x00007f196765c747 __assert_fail_base.cold (libc.so.6 + 0x26747)
                                                  #9  0x00007f196766bbf6 __assert_fail (libc.so.6 + 0x35bf6)
                                                  #10 0x00007f19669967a0 nouveau_pushbuf_data (libdrm_nouveau.so.2 + 0x47a0)
                                                  #11 0x00007f1966996703 nouveau_pushbuf_data (libdrm_nouveau.so.2 + 0x4703)
                                                  #12 0x00007f1966996820 n/a (libdrm_nouveau.so.2 + 0x4820)
                                                  #13 0x00007f1966996c47 n/a (libdrm_nouveau.so.2 + 0x4c47)
                                                  #14 0x00007f196699799a n/a (libdrm_nouveau.so.2 + 0x599a)
                                                  #15 0x00007f1967b759a8 n/a (nouveau_drv.so + 0x249a8)
                                                  #16 0x00007f196695d00b n/a (libexa.so + 0x600b)
                                                  #17 0x00007f1966960655 n/a (libexa.so + 0x9655)
                                                  #18 0x000055e75a550507 miCopyRegion (Xorg + 0x44507)
                                                  #19 0x000055e75a5543c6 miDoCopy (Xorg + 0x483c6)
                                                  #20 0x00007f196695a319 n/a (libexa.so + 0x3319)
                                                  #21 0x000055e75a5d1816 n/a (Xorg + 0xc5816)
                                                  #22 0x00007f1967b5e4bb n/a (nouveau_drv.so + 0xd4bb)
                                                  #23 0x00007f1967b5ec49 n/a (nouveau_drv.so + 0xdc49)
                                                  #24 0x00007f1967b5f25b n/a (nouveau_drv.so + 0xe25b)
                                                  #25 0x000055e75a6cb35d DRI2SwapBuffers (Xorg + 0x1bf35d)
                                                  #26 0x000055e75a6d2613 n/a (Xorg + 0x1c6613)
                                                  #27 0x000055e75a546195 n/a (Xorg + 0x3a195)
                                                  #28 0x00007f196765e152 __libc_start_main (libc.so.6 + 0x28152)
                                                  #29 0x000055e75a5465de _start (Xorg + 0x3a5de)
                                                  
                                                  Stack trace of thread 572:
                                                  #0  0x00007f196752b6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
                                                  #1  0x00007f196562abdc n/a (nouveau_dri.so + 0x4edbdc)
                                                  #2  0x00007f19656293a8 n/a (nouveau_dri.so + 0x4ec3a8)
                                                  #3  0x00007f19675253e9 start_thread (libpthread.so.0 + 0x93e9)
                                                  #4  0x00007f1967736293 __clone (libc.so.6 + 0x100293)
                                                  
                                                  Stack trace of thread 573:
                                                  #0  0x00007f196752b6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
                                                  #1  0x00007f196562abdc n/a (nouveau_dri.so + 0x4edbdc)
                                                  #2  0x00007f19656293a8 n/a (nouveau_dri.so + 0x4ec3a8)
                                                  #3  0x00007f19675253e9 start_thread (libpthread.so.0 + 0x93e9)
                                                  #4  0x00007f1967736293 __clone (libc.so.6 + 0x100293)
                                                  
                                                  Stack trace of thread 574:
                           #0  0x00007f196752b6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
                                                  #1  0x00007f196562abdc n/a (nouveau_dri.so + 0x4edbdc)
                                                  #2  0x00007f19656293a8 n/a (nouveau_dri.so + 0x4ec3a8)
                                                  #3  0x00007f19675253e9 start_thread (libpthread.so.0 + 0x93e9)
                                                  #4  0x00007f1967736293 __clone (libc.so.6 + 0x100293)
                                                  
                                                  Stack trace of thread 575:
                                                  #0  0x00007f196752b6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
                                                  #1  0x00007f196562abdc n/a (nouveau_dri.so + 0x4edbdc)
                                                  #2  0x00007f19656293a8 n/a (nouveau_dri.so + 0x4ec3a8)
                                                  #3  0x00007f19675253e9 start_thread (libpthread.so.0 + 0x93e9)
                                                  #4  0x00007f1967736293 __clone (libc.so.6 + 0x100293)

It looks that is an error in nouveau driver.

$ uname -a
Linux mypc 5.9.14-arch1-1 #1 SMP PREEMPT Sat, 12 Dec 2020 14:37:12 +0000 x86_64 GNU/Linux
$ 

# lshw -class video
  *-display                 
       description: VGA compatible controller
       product: GK208B [GeForce GT 710]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:30 memory:fd000000-fdffffff memory:d0000000-d7ffffff memory:dc000000-ddffffff ioport:ac00(size=128) memory:c0000-dffff
#

# lspci
00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HB (ICH8) 4 port SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)
02:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)
02:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
# 

Has someone similar error?

Regards

Last edited by archlinuxforever (2020-12-29 19:42:58)