'boincmgr' received an X Window System error
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| boinc (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: boinc-manager
BOINC Manager crash since today with these messages :
boincmgr
Skin Manager: Failed to parse static line color. Using default.
Skin Manager: Application name was not defined. Using default.
Skin Manager: Failed to load application logo. Using default.
Skin Manager: Company name was not defined. Using default.
Skin Manager: Company web site was not defined. Using default.
Skin Manager: Project name was not defined. Using default.
Skin Manager: Default tab was not defined. Using default.
Skin Manager: Exit message was not defined. Using default.
Skin Manager: Failed to load attach to project wizard bitmap logo. Using default.
Skin Manager: Attach to project wizard title was not defined. Using default.
Skin Manager: Failed to load attach to project wizard bitmap logo. Using default.
Skin Manager: Attach to project wizard title was not defined. Using default.
Skin Manager: Failed to load 'a' icon. Using default.
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 503 error_code 11 request_code 148 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.)
| David DeHaan (dedehaan) wrote | #1 |
| David DeHaan (dedehaan) wrote | #2 |
I am also experiencing this error:
dedehaan@
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 255 error_code 11 request_code 144 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.)
boincmgr worked fine until I installed updates this morning.
Previous (working) configuration: Ubuntu 6.06, Linux 2.6.15-28-386, xserver-xorg-core 1:1.0.2-0ubuntu10.7
Current (broken) configuration: Ubuntu 6.06, Linux 2.6.15-51-386, xserver-xorg-core 1:1.0.2-0ubuntu10.8
Here is the full list of packages that were upgraded:
libxfont1 1:1.0.0-0ubuntu3.3 1:1.0.0-0ubuntu3.4
xserver-xorg-core 1:1.0.2-0ubuntu10.7 1:1.0.2-0ubuntu10.8
base-files 3.1.9ubuntu7.1 3.1.9ubuntu7.2
libisc11 1:9.3.2-2ubuntu1.3 1:9.3.2-2ubuntu1.4
libdns21 1:9.3.2-2ubuntu1.3 1:9.3.2-2ubuntu1.4
libisccc0 1:9.3.2-2ubuntu1.3 1:9.3.2-2ubuntu1.4
libisccfg1 1:9.3.2-2ubuntu1.3 1:9.3.2-2ubuntu1.4
libbind9-0 1:9.3.2-2ubuntu1.3 1:9.3.2-2ubuntu1.4
liblwres9 1:9.3.2-2ubuntu1.3 1:9.3.2-2ubuntu1.4
bind9-host 1:9.3.2-2ubuntu1.3 1:9.3.2-2ubuntu1.4
dnsutils 1:9.3.2-2ubuntu1.3 1:9.3.2-2ubuntu1.4
libcupsys2 1.2.2-0ubuntu0.
libcupsimage2 1.2.2-0ubuntu0.
cupsys 1.2.2-0ubuntu0.
cupsys-bsd 1.2.2-0ubuntu0.
cupsys-client 1.2.2-0ubuntu0.
linux-image-386 2.6.15.28 2.6.15.51
linux-restricte
linux-386 2.6.15.28 2.6.15.51