The program received an x window system error

Xorg не нравится приложениям

Вот, и vlc что то ругается, и amule не хочет..

$ vlc
VLC media player 0.8.6f Janus
The program ‘.’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadAlloc (insufficient resources for operation)’.
(Details: serial 191 error_code 11 request_code 145 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the —sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
ivan@Panama:/usr/ports/other/vlc$ vlc —sync
VLC media player 0.8.6f Janus
vlc: unknown option or missing mandatory argument `—sync’
Try `vlc —help’ for more information.

$ amule
Initialising aMule
Checking if there is an instance already running.
No other instances are running.
The program ‘amule’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadAlloc (insufficient resources for operation)’.
(Details: serial 595 error_code 11 request_code 145 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the —sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

Re: Xorg не нравится приложениям

Общее в этих двух программах — wxWidgets. Попробуй пересобрать их.

Re: Xorg не нравится приложениям

а лучше не использовать. от пионерской поделки wx завсегда одни проблемы.

Re: Xorg не нравится приложениям

$ pkginfo -i | grep wx
wxgtk 2.8.7-1

Это оно? Его пересобирать то?
/usr/bin/wxrc -> wxrc-2.8
Вот эти исполняемые файлы.. я так понял.

Хм.. пересобирать пробовал, даже на версию 2.8 c 2.6 перешёл. Можно, интересно, указать приложениям работать без неё. То есть, снести её к чертям и пересобрать приложения? Попробую на досуге. Не знаю, правильно ли это и как нормальные люди поступают?

Re: Xorg не нравится приложениям

Удалил..
Теперь VLC ругается в консоль, особенно когда надо открыть файлы через диалоги:

$ vlc
VLC media player 0.8.6f Janus
[00000271] skins2 interface error: no suitable dialogs provider found (hint: compile the wxWidgets plugin, and make sure it is loaded properly)
[00000271] skins2 interface: skin: VLC 0.8.5 Default Skin author: aLtgLasS
[00000271] skins2 interface error: no associated D&D object
[00000271] skins2 interface error: no suitable dialogs provider found (hint: compile the wxWidgets plugin, and make sure it is loaded properly)
[00000271] skins2 interface error: no suitable dialogs provider found (hint: compile the wxWidgets plugin, and make sure it is loaded properly)

amule вообще собираться не хочет:

configure: error:
wxWidgets must be installed on your system but wx-config
script couldn’t be found. Please check that wx-config is
in path or specified by —with-wx-config=path flag, the
directory where wxWidgets libraries are installed (returned
by ‘wx-config —libs’ command) is in LD_LIBRARY_PATH or
equivalent variable and wxWidgets version is 2.6.0 or above.

Короче то им не нак и это не эдак. Задолбали эти быдлозависимости.

Источник

Arch Linux

You are not logged in.

#1 2013-04-23 11:49:21

[SOLVED] Gnome 3.8 apps crash with X Window System Error

So far this applications are affected:
— gnome-terminal (when clicking on menu)
— gnome-control-center (when choosing Users or Date & Time and some other tiles, choosing account in GOA)
— epiphany (when clicking on new tab button)

They crash with following error in console:

dmesg show only this line:

Running with gdb:

My graphic card (iI guess this has something to do with xorg):
AMD Mobility Radeon HD 4550 (using catalyst legacy driver 13.1 with Xorg 1.12)

Last edited by szorti (2013-04-24 08:40:26)

#2 2013-04-24 01:42:29

Re: [SOLVED] Gnome 3.8 apps crash with X Window System Error

Same error here, and same graphic setup as yours.
I have AMD catalyst 13.1 legacy drivers on xorg 1.12 too, and my graphic card is an ATI Radeon HD 4870.

#3 2013-04-24 07:35:32

Re: [SOLVED] Gnome 3.8 apps crash with X Window System Error

I did a little test:
— upgraded to xorg 1.14
— switched from catalyst to xf86-video-ati drive

Most of the errors dissappeared (GOA still crashes).
But now i can only see message tray using keyboard shortcut (super + m). I read that I need to move my mouse fast to the botton edge of my screen — does not work — instead it show up randomly when i moved mouse near the bottom edge.
I don’t want to use the open source drivers (slow and laggy with multi monitor setup I’m using). I hope gnome devs will fix this bugs soon.

SOLUTION (to still use catalyst):
I found out that this is an Xorg 1.12 bug.
Bug: http://lists.debian.org/debian-x/2012/12/msg00133.html

To solve this use patch from this bugreport to compile xorg 1.12
I used this aur packages:
1. https://aur.archlinux.org/packages/xf86 … evdev1.12/
2. https://aur.archlinux.org/packages/xorg-server1.12/ — I have edited PKGBUILD to include patch from bug report above

Last edited by szorti (2013-04-24 08:40:10)

#4 2013-04-24 12:55:20

Re: [SOLVED] Gnome 3.8 apps crash with X Window System Error

Thank you so much, that patch solved the problem.

#5 2013-04-24 13:51:14

Re: [SOLVED] Gnome 3.8 apps crash with X Window System Error

Hi, i’ve the same issue.
How can i apply the patch?

when i run makepkg it returns an error:

Also i’ve installed the old version of this package:

EDIT:
The problem was the package of xorg-server.
I’ve installed the package from [xorg1.12] repository, instead you installed it from AUR.

if i replace it with AUR package, the [xorg1.12] repository is not necessary more?
how can i manage the conflicts with previous Xorg installation ?

sorry for my incompetence!

Last edited by Angelsoul (2013-04-24 14:59:29)

Источник

‘nvidia-settings’ received an X Window System error (error was ‘BadValue (integer parameter out of range for operation)’.)

Since the last apt-get dist-upgrade this morning, I’ve started seeing nvidia-settings crashes when I try setting something with the error below:

Having spent a few hours already I’ve tried several things below and no luck:

/.nvidia-settings-rc —> New file was made at some point I’m not sure.

Since it looks like the latest nvidia driver 331.20 was just released early this morning, I suspect the newly installed library contains a wrongdoer. But does anyone have an idea to fix this?

2 Answers 2

I saw the same issue yesterday. Downgrading from 331.20 to 304.88 worked for me:

Yes, as @Eric suggested downgrading to 304.88 works. As I was on i386 and was missing a few dependencies had to go through a few more steps. The following should solve it for people using i386 .

First download the i386 package

The package has a few dependencies, we need’em installed before dpkg ing the above package. (In my case I was missing nvidia-installer-cleanup and libxnvctrl0 ):

In order to dpkg — nvidia-installer-cleanup , we need to do a little clean-up.

After the above packages have been removed you can dpkg the downloaded packages one by one.

Once, you have rolled back to version 304.88 and do not want it to update it, you can lock the version as follows:

In future, if you’d want to remove the hold, you can do:

NOTE: You can also use the synaptic package manager. Just select your package, and from the package menu select Lock Version .

Источник

Ubuntu Wiki

XError

Symptoms

• The client app crashes with a message like this one (Gdk):

Non-Symptoms

• The X Server itself locks up or crashes. This is a much more severe issue. In this case your app has gotten X into some funky state. See some of the other X/Troubleshooting pages to sort this out.

How It Works

X11 is a client/server protocol. Client applications (like Gdk or Qt programs) send requests to the X server to update the screen, get information, and so on. The server does its best to honor these requests, however in some cases it can’t be done, and an X error is returned to the client instead.

It’s actually quite common and normal for the X server to return errors to let the client know certain things can’t be done. Most of the time, typically the client app (or one of its underlying libraries) would listen for that error and handle it appropriately.

So what you’re seeing with the above error message is a situation where an unexpected error was returned which the client app was *not* prepared to handle. There are a few different angles for dealing with it.

Tracing X Protocol Communication

The program xtrace can be used to examine the request/response traffic between your client and the X Server.

More info about xtrace can be found at Debian

(A walkthrough usage example would be handy here. )

Problem: Client App Needs to Handle X Error

Linux systems exist in great diversity, and it is quite usual for people to run a client app on a system which is very different from the one the app was developed on. Maybe compositing or DRI is turned off and thus unavailable, or the system has an unusual architecture. Thus client apps need to be prepared to handle the range of errors that X can return, and to trigger an appropriate action (such as displaying an error dialog, or using alternate functionality.)

Here’s a snippet of code showing one way to catch x11 errors in gdk (stolen from Bug #521371):

Problem: Client App Speaks Wrong Protocol

The X Server (specifically, libx11/libxcb) defines the protocol language used and commands that client applications can use in communicating with the server. So as a first order analysis, doublecheck that the API (function calls, parameter types and values, etc.) are consistent with the shipped version of libx11. In general, this can be checked by referring to the installed man page for the given X command.

Another thing to check is if the protocol has changed, such as due to a bug in the API or other development activity. Generally this situation would only arise in the development version of Ubuntu when we upgrade to a new xorg-server and/or libx11 package. This should be a pretty rare situation that it’d result in breakage at the client level, but it does happen from time to time. If you suspect a protocol change, upgrading/downgrading these can be done to verify it as the cause of the client breakage.

Problem: X Server Returned an Unexpected Error

In some rare cases, the xserver might return an error code that is not documented in the man page. This is a bug, either in the documentation (package libx11) or the xserver itself (package xorg-server).

Useful information to include in the bug report includes:

• Xorg.0.log after reproducing the issue
• Full backtrace from the client
• xtrace output

X/Troubleshooting/XError (последним исправлял пользователь static-50-53-79-63 2012-04-14 02:28:01)

Источник

Firefox stopped working with a BadAlloc X Window System Error on Ubuntu 21.10

My Firefox has stopped working out of the blue. I am on Ubuntu 21.10. Not sure if it was after a recent update. I have to assume it was. When I checked gnome menu editor, I see that the command in the .desktop file to run is env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/firefox_firefox.desktop /snap/bin/firefox %u so I figure I run it in the terminal and see what the error is. The error is the following below

Now interestingly, when I run Firefox in safe mode, it works! I have no idea why. I refreshed settings to default, and turned off all the extensions while in safe mode and reran it normally and I’m still getting that error. It’s weird.

Does anyone have any suggestions? Also where do I file a bug?

3 Answers 3

I experienced this exact error in a fresh install of Ubuntu 21.10 with the snap Firefox package. I switched to the apt package and it resolved the problem. However, I upgraded to 22.04, and the apt Firefox package is no longer available, and again faced this error.

I tried everything vanadium recommended without success. I noticed that the error complains of a problem with X Window System. When I checked Firefox’s troubleshooting page in safe mode, I noticed that safe mode disables WebGL. I made a guess, switched from the X.Org Nouveau display driver to the proprietary NVIDIA driver nvidia-driver-510, restarted, and the error resolved.

I suspect a bug in the Nouveau driver.

How to switch from the X.Org Nouveau display driver to the proprietary NVIDIA driver:

1. list available drivers: sudo ubuntu-drivers devices
2. find the distro non-free recommended one
3. install it: sudo apt-get install nvidia-driver-510
4. restart

Источник

I’m running Ubuntu 14.04, atom 0.194.0. When Reloading from the View menu, atom crashes, with the following error:

[13844:0423/122425:ERROR:browser_main_loop.cc(170)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[13844:0423/122426:ERROR:nss_util.cc(819)] After loading Root Certs, loaded==false: NSS error code: -8018
[13844:0423/122426:ERROR:bus.cc(431)] Failed to connect to the bus: Failed to connect to socket /tmp/dbus-SpLUr3eGBR: Connection refused
App load time: 306ms
[13881:0423/122426:INFO:renderer_main.cc(212)] Renderer process started
[13844:0423/122426:INFO:CONSOLE(111)] "You are using PusherJS client authentication. Never ever use this for a production application, as it would expose your secret keys.", source: /home/matt/.atom/packages/atom-pair/lib/pusher/pusher-js-client-auth.js (111)
[13844:0423/122428:INFO:CONSOLE(9)] "activate linter-coffeelint", source: /home/matt/.atom/packages/linter-coffeelint/lib/init.coffee (9)
[13844:0423/122428:INFO:CONSOLE(18)] "activate linter-eslint", source: /home/matt/.atom/packages/linter-eslint/lib/init.coffee (18)
[13844:0423/122428:INFO:CONSOLE(59)] "Window load time: 2673ms", source: file:///usr/share/atom/resources/app.asar/static/index.js (59)
[13844:0423/122430:ERROR:bus.cc(431)] Failed to connect to the bus: Failed to connect to socket /tmp/dbus-SpLUr3eGBR: Connection refused
[13844:0423/122432:ERROR:bus.cc(431)] Failed to connect to the bus: Failed to connect to socket /tmp/dbus-SpLUr3eGBR: Connection refused
[13974:0423/122434:INFO:renderer_main.cc(212)] Renderer process started
[13844:0423/122434:ERROR:bus.cc(431)] Failed to connect to the bus: Failed to connect to socket /tmp/dbus-SpLUr3eGBR: Connection refused
[13844:0423/122434:INFO:CONSOLE(111)] "You are using PusherJS client authentication. Never ever use this for a production application, as it would expose your secret keys.", source: /home/matt/.atom/packages/atom-pair/lib/pusher/pusher-js-client-auth.js (111)
[13844:0423/122436:INFO:CONSOLE(9)] "activate linter-coffeelint", source: /home/matt/.atom/packages/linter-coffeelint/lib/init.coffee (9)
[13844:0423/122436:INFO:CONSOLE(18)] "activate linter-eslint", source: /home/matt/.atom/packages/linter-eslint/lib/init.coffee (18)
[13844:0423/122437:INFO:CONSOLE(59)] "Window load time: 2679ms", source: file:///usr/share/atom/resources/app.asar/static/index.js (59)
[13844:0423/122439:ERROR:bus.cc(431)] Failed to connect to the bus: Failed to connect to socket /tmp/dbus-SpLUr3eGBR: Connection refused
The program 'atom' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 946 error_code 8 request_code 42 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Symptoms

• The client app crashes with a message like this one (Gdk):

Gdk-ERROR **: The program '<PROGRAM>' received an X Window System error.
This probably reflects a bug in the program.
The error was '<SOME_ERROR>'.
  (Details: serial <AA> error_code <B> request_code <CC> minor_code <D>)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...

• Or like this (Qt):

X Error: <SOME_ERROR>
  Major opcode:  <CC>
  Minor opcode:  <D>
  Resource id:  0x0
Failed to open device

Non-Symptoms

• The X Server itself locks up or crashes. This is a much more severe issue. In this case your app has gotten X into some funky state. See some of the other X/Troubleshooting pages to sort this out.

How It Works

X11 is a client/server protocol. Client applications (like Gdk or Qt programs) send requests to the X server to update the screen, get information, and so on. The server does its best to honor these requests, however in some cases it can’t be done, and an X error is returned to the client instead.

It’s actually quite common and normal for the X server to return errors to let the client know certain things can’t be done. Most of the time, typically the client app (or one of its underlying libraries) would listen for that error and handle it appropriately.

So what you’re seeing with the above error message is a situation where an unexpected error was returned which the client app was *not* prepared to handle. There are a few different angles for dealing with it.

Tracing X Protocol Communication

The program xtrace can be used to examine the request/response traffic between your client and the X Server.

More info about xtrace can be found at Debian

(A walkthrough usage example would be handy here…)

Problem: Client App Needs to Handle X Error

Linux systems exist in great diversity, and it is quite usual for people to run a client app on a system which is very different from the one the app was developed on. Maybe compositing or DRI is turned off and thus unavailable, or the system has an unusual architecture. Thus client apps need to be prepared to handle the range of errors that X can return, and to trigger an appropriate action (such as displaying an error dialog, or using alternate functionality.)

Here’s a snippet of code showing one way to catch x11 errors in gdk (stolen from Bug #521371):

  gdk_error_trap_push();

  resources = XRRGetScreenResources (screen_x11->xdisplay,
                                     screen_x11->xroot_window);
  gdk_flush();
  
  if (gdk_error_trap_pop())
    return FALSE; 
  
  if (!resources)
    return FALSE;

Problem: Client App Speaks Wrong Protocol

The X Server (specifically, libx11/libxcb) defines the protocol language used and commands that client applications can use in communicating with the server. So as a first order analysis, doublecheck that the API (function calls, parameter types and values, etc.) are consistent with the shipped version of libx11. In general, this can be checked by referring to the installed man page for the given X command.

Another thing to check is if the protocol has changed, such as due to a bug in the API or other development activity. Generally this situation would only arise in the development version of Ubuntu when we upgrade to a new xorg-server and/or libx11 package. This should be a pretty rare situation that it’d result in breakage at the client level, but it does happen from time to time. If you suspect a protocol change, upgrading/downgrading these can be done to verify it as the cause of the client breakage.

Problem: X Server Returned an Unexpected Error

In some rare cases, the xserver might return an error code that is not documented in the man page. This is a bug, either in the documentation (package libx11) or the xserver itself (package xorg-server).

Useful information to include in the bug report includes:

• Xorg.0.log after reproducing the issue
• Full backtrace from the client
• xtrace output

Binary package hint: firefox-3.0

URL: http://lady.mail.ru/article/45677

When I trying to load speciefied url, firefox (3.0b5) >>DIES<< spitting this on console:
— 8< — 8< —
The program ‘firefox’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadAlloc (insufficient resources for operation)’.
  (Details: serial 448479 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the —sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
— >8 — >8 —

I tried to start firefox with —sync and it tells almost the same message:
— 8< — 8< —
The program ‘firefox’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadAlloc (insufficient resources for operation)’.
  (Details: serial 61109 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the —sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

— >8 — >8 —

Now context.
1)19:47:dvl:~/dl$ lsb-release -rd
lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04

2) 19:47:dvl:~/dl$ apt-cache policy firefox
firefox:
  Installed: 3.0~b5+nobinonly-0ubuntu3
  Candidate: 3.0~b5+nobinonly-0ubuntu3
  Version table:
 *** 3.0~b5+nobinonly-0ubuntu3 0
        500 ftp://au.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: amd64
Date: Tue May 13 19:42:43 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: nvidia
Package: firefox-3.0 3.0~b5+nobinonly-0ubuntu3
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=/home/username/inferno/Linux/386/bin:/home/username/bin:/opt/mono-1.2.3.1/bin:/usr/local/bin:/home/username/lib/java-current/bin:/usr/local/:/usr/X11R6/bin:/home/username/open64/bin:/home/username/inferno/Linux/386/bin:/home/username/bin:/opt/mono-1.2.3.1/bin:/usr/local/bin:/home/username/lib/java-current/bin:/usr/local/:/usr/X11R6/bin:/home/username/open64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-16-generic x86_64