[opensuse] BadAlloc in gtk programs
Hello, some gtk programs e.g. eclipse, apache directory studio, amule, ... I get this error: The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 651 error_code 11 request_code 149 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 error occurs few days ago when I updated X-org. I am using opensuse 10.3 thanks, m.
Dňa Monday 21 January 2008 09:10:41 Michal Hlavac ste napísal:
Hello,
some gtk programs e.g. eclipse, apache directory studio, amule, ... I get this error:
The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 651 error_code 11 request_code 149 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 error occurs few days ago when I updated X-org. I am using opensuse 10.3
on the other hand some programs work (firefox, thunderbird)... m.
On Monday 21 January 2008 02:14:50 am Michal Hlavac wrote:
Dňa Monday 21 January 2008 09:10:41 Michal Hlavac ste napísal:
Hello,
some gtk programs e.g. eclipse, apache directory studio, amule, ... I get this error:
The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 651 error_code 11 request_code 149 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 error occurs few days ago when I updated X-org. I am using opensuse 10.3
on the other hand some programs work (firefox, thunderbird)...
m.
The same here with XaraLX. ~> xara The program 'xara' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 5991 error_code 11 request_code 147 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.) -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Jan 21, 2008 at 03:05:22AM -0600, Rajko M. wrote:
On Monday 21 January 2008 02:14:50 am Michal Hlavac wrote:
Dňa Monday 21 January 2008 09:10:41 Michal Hlavac ste napísal:
Hello,
some gtk programs e.g. eclipse, apache directory studio, amule, ... I get this error:
The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 651 error_code 11 request_code 149 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 error occurs few days ago when I updated X-org. I am using opensuse 10.3
on the other hand some programs work (firefox, thunderbird)...
m.
The same here with XaraLX.
~> xara The program 'xara' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 5991 error_code 11 request_code 147 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 is https://bugzilla.novell.com/show_bug.cgi?id=345131 Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 21 January 2008 03:19:07 am Marcus Meissner wrote: ...
The workaround in comment #36 fixes problem temporarily. Section "Extensions" Option "MIT-SHM" "no" EndSection It is too late to test fixed xorg. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Marcus Meissner -
Michal Hlavac -
Rajko M.