Announcement

Collapse
No announcement yet.

X errors and crashes

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    X errors and crashes

    So, ever since my upgrade to Feisty, many applications won't start (for example Firefox, or Synaptic), and any kind of OpenGL (Beryl, screen savers) will actually cause a crash and re-start of the X server. Here's what I'm getting as an error from firefox, for example - the error is the same with any application that won't start:


    QPainter::begin: Cannot paint null pixmap
    QPainter::setPen: Will be reset by begin()
    QPainter::setFont: Will be reset by begin()
    QPainter::end: Missing begin() or begin() failed
    The program 'firefox-bin' received an X Window System error.
    This probably reflects a bug in the program.
    The error was 'BadValue (integer parameter out of range for operation)'.
    (Details: serial 471 error_code 2 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.)


    I'm running a GeForce6600 with the latest drivers from the NVIDIA website.
    Any hints would be greatly appreciated!

    [EDIT] after installing the 9746 drivers instead of 9755, OpenGL doesn't crash the X server anymore. However, the X error pasted above is still there.

    #2
    Re: X errors and crashes

    Update: I have a feeling that this is somehow related to the GTK libraries, or the ones that pipe GTK through QT, since firefox, synaptic and beryl-manager (which now produces said X error instead of crashing X) are all GTK applications. I've tried reinstalling all GTK and QT libs, to no avail. Any takers?

    Comment


      #3
      Re: X errors and crashes

      Another update: uninstalling gtk-qt-engine fixes the problem (of course then GTK apps look pretty bad, but at least they don't crash ). So, there seems to be a bug in gtk-qt-engine...

      Comment


        #4
        Re: X errors and crashes

        I just received the same error, and fixed it following the above instructions (I somewhat recently upgraded from Feisty to Gutsy). The error Konsole gave me was as follows:
        ~$ firefox
        QPainter::begin: Cannot paint null pixmap
        QPainter::setPen: Will be reset by begin()
        QPainter::setFont: Will be reset by begin()
        QPainter::end: Missing begin() or begin() failed
        The program 'firefox-bin' received an X Window System error.
        This probably reflects a bug in the program.
        The error was 'BadValue (integer parameter out of range for operation)'.
        (Details: serial 449 error_code 2 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.)
        Asus G1S-X3:
        Intel Core2 Duo T7500, Nvidia GeForce 8600M GT, 4Gb PC2-5300, 320Gb Hitachi 7k320, Linux ( )

        Comment


          #5
          Re: X errors and crashes

          Update: The error seems to be with the KDE style -> GTK apps, because if I choose another style that is GTK specific, such as Clearlooks, my GTK apps work fine. However, if I choose the Use my KDE style in GTK applications option, or select the QT (not QTCurve) style, my GTK apps won't open and give me the error code listed above.
          Asus G1S-X3:
          Intel Core2 Duo T7500, Nvidia GeForce 8600M GT, 4Gb PC2-5300, 320Gb Hitachi 7k320, Linux ( )

          Comment

          Working...
          X