Bug 14279 - Gdk-ERROR **: The program '_______' received an X Window System error
Summary: Gdk-ERROR **: The program '_______' received an X Window System error
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-14 04:04 CEST by Curtis Hildebrand
Modified: 2015-05-19 21:15 CEST (History)
0 users

See Also:
Source RPM: gdk-pixbuf2.0-2.31.1-3.mga5.src.rpm
CVE:
Status comment:


Attachments

Description Curtis Hildebrand 2014-10-14 04:04:21 CEST
Description of problem:

I receive the exact same error when trying to run gtkpod and gnome-control-center from the commandline.  I don't know if the problem is with the programs or with GDK.  I'm running them from within KDE.

]$ gnome-control-center 

(gnome-control-center:12685): Gdk-ERROR **: The program 'gnome-control-center' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 440 error_code 1 request_code 156 (GLX) minor_code 19)
  (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 GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap
[curtis@Parkes SPECS]$ gtkpod

(gtkpod:12704): Gdk-ERROR **: The program 'gtkpod' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 440 error_code 1 request_code 156 (GLX) minor_code 19)
  (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 GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap


Reproducible: 

Steps to Reproduce:
Comment 1 Curtis Hildebrand 2014-10-14 04:05:51 CEST
Also, a local rebuild of gtkpod did not fix the problem.
Comment 2 Curtis Hildebrand 2014-10-16 07:51:26 CEST
I was using the fglrx driver.  After switching to "ati", both programs (and I'm sure others) now work.

Resolve or re-assign the bug as you see fit.

Severity: major => normal

Comment 3 Samuel Verschelde 2015-05-19 21:15:53 CEST
(In reply to Curtis Hildebrand from comment #2)
> I was using the fglrx driver.  After switching to "ati", both programs (and
> I'm sure others) now work.
> 
> Resolve or re-assign the bug as you see fit.

Closing, just reopen if you want it and it's still valid in latest cauldron.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.