Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#9268 - xorg-server BadAlloc error
Attached to Project:
Arch Linux
Opened by Adam Pawelec (proktor) - Saturday, 19 January 2008, 21:55 GMT
Last edited by Jan de Groot (JGC) - Sunday, 20 January 2008, 00:10 GMT
Opened by Adam Pawelec (proktor) - Saturday, 19 January 2008, 21:55 GMT
Last edited by Jan de Groot (JGC) - Sunday, 20 January 2008, 00:10 GMT
|
DetailsSummary and Info:
After xorg-server (I think) update some apps doesn't start. When I try to run wxMaxima or Eclipse I get: The program 'wxmaxima' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 207 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.) The same with Eclipse: The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1041 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.) |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 20 January 2008, 00:10 GMT
Reason for closing: Duplicate
Additional comments about closing: See bug
9254
Sunday, 20 January 2008, 00:10 GMT
Reason for closing: Duplicate
Additional comments about closing: See
Comment by Dan McGee (toofishes) -
Saturday, 19 January 2008, 22:29 GMT
- Field changed: Attached to Project (Pacman → Arch Linux)
Definitely not a pacman bug. Please attach to the correct project next time.
Comment by Mika Hynnä (ighea) -
Saturday, 19 January 2008, 22:54 GMT
This seems to happen after upgrading to xorg-server-1.4.0.90-4 and downgrading back to xorg-server-1.4.0.90-3 "fixes" the problem so far.