Running Pdaxrom 1.1.0 Beta 3 In Chroot Under X/qt Options

[ShiroiKuma]

I tried it and it works... sorta. Seems there is a render problem with the X/Qt X-server.

For instance, if I run Firefox 1.5, this is the screen I see:  sc_2006_4_14_04.43.31.png ( 22.78K ) Number of downloads: 146


Firefox doesn't report any errors though. But running Leafpad, you get basically the same messed screen, and this error:

CODE

Gdk-WARNING **: The X server advertises that RENDER support is present,
but fails to supply the necessary pixmap support. In
other words, it is buggy.
The program 'leafpad' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
   (Details: serial 865 error_code 143 request_code 138 minor_code23)
    (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.)

and bombs out.

How can I fix this? Some command-line option when starting X/Qt? Install some missing package?

[Meanie]

I tried it and it works... sorta. Seems there is a render problem with the X/Qt X-server.

For instance, if I run Firefox 1.5, this is the screen I see:  sc_2006_4_14_04.43.31.png ( 22.78K ) Number of downloads: 146


Firefox doesn't report any errors though. But running Leafpad, you get basically the same messed screen, and this error:

CODE

Gdk-WARNING **: The X server advertises that RENDER support is present,
but fails to supply the necessary pixmap support. In
other words, it is buggy.
The program 'leafpad' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
   (Details: serial 865 error_code 143 request_code 138 minor_code23)
    (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.)

and bombs out.

How can I fix this? Some command-line option when starting X/Qt? Install some missing package?

the libXrender library in xqt is buggy. you need to install the patch available from my site

[ShiroiKuma]

the libXrender library in xqt is buggy. you need to install the patch available from my site

I just installed your patch, but I still get the same error... ?

[ShiroiKuma]

Well, I'm almost sure it doesn't work now, unless I've missed something big.

I've fiddled with it for hours, even did a clean reflash, and installed your jumbo-xqt package, but the error is still the same.

Looks like the pdaXrom chrooted, at least on the SL-C3200, is a no-go.

Unless one could use keypebble, I guess...

I've never used keypebble, and have searched the forum, it's got tons of posts from users about it, but I couldn't find a clear step-by-step idiot guide, i.e. install these packages, then run this with these parameters, and then this, and that's how you get X in keypebble.

Could someone write this here briefly?

[Meanie]

Well, I'm almost sure it doesn't work now, unless I've missed something big.

I've fiddled with it for hours, even did a clean reflash, and installed your jumbo-xqt package, but the error is still the same.

Looks like the pdaXrom chrooted, at least on the SL-C3200, is a no-go.

Unless one could use keypebble, I guess...

I've never used keypebble, and have searched the forum, it's got tons of posts from users about it, but I couldn't find a clear step-by-step idiot guide, i.e. install these packages, then run this with these parameters, and then this, and that's how you get X in keypebble.

Could someone write this here briefly?

That's a pity. I was thinking about trying chrooted pdaXrom on Sharp ROM as an easy way out, sigh
well, back to hacking pdaXQtrom... seems like I have to recompile a lot of apps for it to work. The biggest problem is gtk+ and glib compatability. I thought I had it all working but something screwed up so I am starting again and building it from scratch...

[ShiroiKuma]

That's a pity. I was thinking about trying chrooted pdaXrom on Sharp ROM as an easy way out, sigh
well, back to hacking pdaXQtrom... seems like I have to recompile a lot of apps for it to work. The biggest problem is gtk+ and glib compatability. I thought I had it all working but something screwed up so I am starting again and building it from scratch...

Is it worth it? What would be the benefit over chrooted debian in this case? Speed increase?