[gentoo-user] X.org is b0rked - BadIdChoice

[gentoo-user] X.org is b0rked - BadIdChoice

[Bruno Lustosa]

Hello.

After the last upgrade, X is completely broken. I can start it, but
applications randomly crash. In fact, not so randomly. It's almost as
if I was running xkill. If I click on the background, nautilus dies.
If I click the panel, it dies. Applications that are run directly will
also crash after a few seconds.
I don't know how to start, but it seems to be a X.org issue, as it
happens with other window managers as well, and even without a window
manager (tried to start X with just a xterm).
I tried to google for 'BadIdChoice', but couldn't find much.
I also tried to upgrade from xorg 7 to 7.1, but this still causes the
same errors.
Can anyone help me with these?
These are the kind of errors that show up on the console:

X Window System Version 7.1.0
Release Date: 22 May 2006
X Protocol Version 11, Revision 0, Release 7.1
Build Operating System: Linux 2.6.16-gentoo-r3 i686
Current Operating System: Linux ti03 2.6.16-gentoo-r3 #5 PREEMPT Wed
May 3 14:52:59 BRT 2006 i686
Build Date: 03 July 2006
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.2.log", Time: Mon Jul  3 14:13:45 2006
(==) Using config file: "/etc/X11/xorg.conf"
(EE) AIGLX: Screen 0 is not DRI capable
    xkb_keycodes             { include "xfree86(abnt2)+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc104)+br" };
    xkb_geometry             { include "pc(abnt2)" };
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
SESSION_MANAGER=local/ti03:/tmp/.ICE-unix/20880
The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 1586 error_code 14 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.)
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 1708 error_code 188 request_code 154 minor_code 6)
  (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 application 'gnome-session' lost its connection to the display :2.0;
most likely the X server was shut down or you killed/destroyed
the application.
Window manager warning: Lost connection to the display ':2.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
xinit:  connection to X server lost.
The application 'nautilus' lost its connection to the display :2.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'gnome-panel' lost its connection to the display :2.0;
most likely the X server was shut down or you killed/destroyed


-- 
Bruno Lustosa <bruno@lustosa.net>
ZCE - Zend Certified Engineer - PHP!
http://www.lustosa.net/
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] X.org is b0rked - BadIdChoice

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 299 bytes --]

Bruno Lustosa wrote:
> The program 'gnome-panel' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'RenderBadPicture (invalid Picture parameter)'.

Try rebuilding renderproto, libXrender, xorg-server, and whatever apps die.

Thanks,
Donnie


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: [gentoo-user] X.org is b0rked - BadIdChoice

[Bruno Lustosa]

On 7/3/06, Donnie Berkholz <spyderous@gentoo.org> wrote:
> Bruno Lustosa wrote:
> > The program 'gnome-panel' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'RenderBadPicture (invalid Picture parameter)'.
>
> Try rebuilding renderproto, libXrender, xorg-server, and whatever apps die.

I *just* found out what was wrong.
The bozo package was libX11. To merge the old version I had to merge
the old xproto though.
This was very very hard to find out. Perhaps someone ought to add
libX11 to that mask list so that people who want to stick to xorg-7.0
doesn't accidentally merge newer version of libX11 without having
xorg-7.1.
I'm adding >=libX11-1.0.3 to my packages.mask.

-- 
Bruno Lustosa <bruno@lustosa.net>
ZCE - Zend Certified Engineer - PHP!
http://www.lustosa.net/
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] X.org is b0rked - BadIdChoice

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

Bruno Lustosa wrote:
> I *just* found out what was wrong.
> The bozo package was libX11. To merge the old version I had to merge
> the old xproto though.
> This was very very hard to find out. Perhaps someone ought to add
> libX11 to that mask list so that people who want to stick to xorg-7.0
> doesn't accidentally merge newer version of libX11 without having
> xorg-7.1.
> I'm adding >=libX11-1.0.3 to my packages.mask.

It's ~arch, you shouldn't get it unless you're running an ~arch system
or specifically added it to package.keywords.

I don't think it should be tied into having anything else upgraded, with
the exception of xproto 7.0.7, so I'm a bit surprised you're hitting
these bugs. Good job tracking it down, though.

Thanks,
Donnie


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: [gentoo-user] X.org is b0rked - BadIdChoice

[Bruno Lustosa]

On 7/3/06, Donnie Berkholz <spyderous@gentoo.org> wrote:
> It's ~arch, you shouldn't get it unless you're running an ~arch system
> or specifically added it to package.keywords.

I am.
My system is all ~x86, except for gcc, glibc and binutils, because I
had an awful experience with those in the past, which left the system
completely unusable. glibc problems aren't something we want to have
to deal with (even python didn't run, so no portage to help).

> I don't think it should be tied into having anything else upgraded, with
> the exception of xproto 7.0.7, so I'm a bit surprised you're hitting
> these bugs. Good job tracking it down, though.

Yes, perhaps instead of masking individual package versions, I should
leave some of those packages tied to x86, that would still allow some
updates.
Anyway, I have the habit of looking at package.* and recheck if things
still need to be there. For example, I still have the unmasks for
gnome-2.14, which I think aren't needed anymore, so I'll remove them.

-- 
Bruno Lustosa <bruno@lustosa.net>
ZCE - Zend Certified Engineer - PHP!
http://www.lustosa.net/
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] X.org is b0rked - BadIdChoice

[Bruno Lustosa]

Hello.

After the last upgrade, X is completely broken. I can start it, but
applications randomly crash. In fact, not so randomly. It's almost as
if I was running xkill. If I click on the background, nautilus dies.
If I click the panel, it dies. Applications that are run directly will
also crash after a few seconds.
I don't know how to start, but it seems to be a X.org issue, as it
happens with other window managers as well, and even without a window
manager (tried to start X with just a xterm).
I tried to google for 'BadIdChoice', but couldn't find much.
I also tried to upgrade from xorg 7 to 7.1, but this still causes the
same errors.
Can anyone help me with these?
These are the kind of errors that show up on the console:

X Window System Version 7.1.0
Release Date: 22 May 2006
X Protocol Version 11, Revision 0, Release 7.1
Build Operating System: Linux 2.6.16-gentoo-r3 i686
Current Operating System: Linux ti03 2.6.16-gentoo-r3 #5 PREEMPT Wed
May 3 14:52:59 BRT 2006 i686
Build Date: 03 July 2006
       Before reporting problems, check http://wiki.x.org
       to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
       (++) from command line, (!!) notice, (II) informational,
       (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.2.log", Time: Mon Jul  3 14:13:45 2006
(==) Using config file: "/etc/X11/xorg.conf"
(EE) AIGLX: Screen 0 is not DRI capable
   xkb_keycodes             { include "xfree86(abnt2)+aliases(qwerty)" };
   xkb_types                { include "complete" };
   xkb_compatibility        { include "complete" };
   xkb_symbols              { include "pc(pc104)+br" };
   xkb_geometry             { include "pc(abnt2)" };
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
SESSION_MANAGER=local/ti03:/tmp/.ICE-unix/20880
The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
 (Details: serial 1586 error_code 14 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.)
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
 (Details: serial 1708 error_code 188 request_code 154 minor_code 6)
 (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 application 'gnome-session' lost its connection to the display :2.0;
most likely the X server was shut down or you killed/destroyed
the application.
Window manager warning: Lost connection to the display ':2.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
xinit:  connection to X server lost.
The application 'nautilus' lost its connection to the display :2.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'gnome-panel' lost its connection to the display :2.0;
most likely the X server was shut down or you killed/destroyed

-- 
Bruno Lustosa <bruno@lustosa.net>
ZCE - Zend Certified Engineer - PHP!
http://www.lustosa.net/
-- 
gentoo-user@gentoo.org mailing list