[opensuse-security] Re: [security-announce] SUSE Security Announcement: Xorg and XFree (SUSE-SA:2008:003)
SUSE Security Announcement
Package: Xorg and XFree Announcement ID: SUSE-SA:2008:003 Date: Thu, 17 Jan 2008 15:00:00 +0000 Affected Products: SUSE LINUX 10.1 openSUSE 10.2 openSUSE 10.3
This update also breaks the graphical user interface of the BOINC software (seti@home, einstein@home etc.). Before the update the program worked without errors; now I get the following message when starting the program: The program 'boincmgr' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 586 error_code 11 request_code 146 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-compiling of the program did not help. Any ideas how to fix this? Bye, Jürgen
On Fri, Jan 18, 2008 at 11:32:25PM +0100, Jürgen Mell wrote:
SUSE Security Announcement
Package: Xorg and XFree Announcement ID: SUSE-SA:2008:003 Date: Thu, 17 Jan 2008 15:00:00 +0000 Affected Products: SUSE LINUX 10.1 openSUSE 10.2 openSUSE 10.3
This update also breaks the graphical user interface of the BOINC software (seti@home, einstein@home etc.). Before the update the program worked without errors; now I get the following message when starting the program:
The program 'boincmgr' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 586 error_code 11 request_code 146 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-compiling of the program did not help. Any ideas how to fix this?
This is a fallout of the Xorg-SHM security patch included. Bugzilla is https://bugzilla.novell.com/show_bug.cgi?id=345131 We will be releasing fixed packages after the weekend (after fix, checkin and QA and release). For now revert the security patch local if necessary. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
participants (2)
-
Jürgen Mell -
Marcus Meissner