After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 749303 - Totem Won't Start on X11
Totem Won't Start on X11
Status: RESOLVED DUPLICATE of bug 747489
Product: totem
Classification: Core
Component: general
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-05-13 11:16 UTC by Antoine Saroufim
Modified: 2015-05-13 11:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Antoine Saroufim 2015-05-13 11:16:58 UTC 
Totem will not start on X11. It will always crash on startup and will display this error: 

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 669 error_code 8 request_code 154 (GLX) minor_code 31)
  (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.)

There is a workaround for it and it's to specify the X11 backend for clutter via the command line. 

There are two threads on the Archlinux forums about this:
https://bbs.archlinux.org/viewtopic.php?id=196029
https://bbs.archlinux.org/viewtopic.php?id=195901

I'm experiencing this bug on openSUSE Tumbleweed
Comment 1 Bastien Nocera 2015-05-13 11:25:03 UTC 
NVidia drivers?
Comment 2 Antoine Saroufim 2015-05-13 11:28:10 UTC 
Yes. I'm using the proprietary driver.
Comment 3 Bastien Nocera 2015-05-13 11:40:15 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 747489 ***