Qt program crashes on Feisty Fawn due to X server

Bug #116625 reported by amuls
4
Affects Status Importance Assigned to Milestone
qt4-x11 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I just received a new Dell Inspiron 9400 PC with a ATI Technologies
Inc Radeon Mobility X1400 graphics card. I installed Kubuntu as I had
on my previous PC (Dell Inspiron 9300) and recompiled our program.

Now I get the errors:

W: X Error: BadRequest (invalid request code or no such operation) 1
  Extension: 219 (Uknown extension)
  Minor opcode: 0 (Unknown request)
  Resource id: 0x1
W: X Error: BadRequest (invalid request code or no such operation) 1
  Extension: 210 (Uknown extension)
  Minor opcode: 0 (Unknown request)
  Resource id: 0x1
W: X Error: BadRequest (invalid request code or no such operation) 1
  Major opcode: 125 ()
  Resource id: 0x1
W: X Error: BadLength (poly request too large or internal Xlib length
error) 16
  Major opcode: 119 (X_GetModifierMapping)
  Resource id: 0x1

I tried several thinsg, such as a reconfigure of the xserver-xorg, but
in vain. After googling around and trying to run the program, I have a
suspiscion that it is a threading problem. It only occurs (so I
think) when I enter or leave a renderthread that creates a pixmap
for the plot we make.

I also noticed that similar warnings are generated by a Fedora Core 5 system,
but without the program crashing.

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi amuls, thanks for reporting this bug. From googling on that error message, it sounds like the bug occurs in Qt when using a non-XCB-enabled xlib.

http://lists.trolltech.com/qt4-preview-feedback/2005-09/msg00037.html

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Kubuntu Fiesty Fawn has reached the end of it's 18 month supported life. Does this bug still occur for you in a more recent version of Kubuntu?

Changed in qt4-x11:
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in qt4-x11:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.