Version-Release number of selected component: totem-3.16.0-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/totem --gapplication-service crash_function: _g_log_abort executable: /usr/bin/totem global_pid: 15145 kernel: 4.0.0-1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:315 #9 XInternAtoms at IntAtom.c:283 #10 _gdk_x11_precache_atoms at gdkproperty-x11.c:239 #11 base_precache_atoms at gdkdnd-x11.c:1541 #12 _gdk_x11_window_register_dnd at gdkdnd-x11.c:2393 #17 gtk_widget_realize at gtkwidget.c:5525 #18 video_widget_create at totem-object.c:4077 #19 totem_object_app_activate at totem-object.c:197 #20 _g_closure_invoke_va at gclosure.c:831 #23 g_application_activate at gapplication.c:2111
Created attachment 1018822 [details] File: backtrace
Created attachment 1018823 [details] File: cgroup
Created attachment 1018824 [details] File: core_backtrace
Created attachment 1018825 [details] File: dso_list
Created attachment 1018826 [details] File: environ
Created attachment 1018827 [details] File: limits
Created attachment 1018828 [details] File: maps
Created attachment 1018829 [details] File: mountinfo
Created attachment 1018830 [details] File: namespaces
Created attachment 1018831 [details] File: open_fds
Created attachment 1018832 [details] File: proc_pid_status
Created attachment 1018833 [details] File: var_log_messages
definitely related to: https://bugzilla.gnome.org/show_bug.cgi?id=747489
What makes you think that it is ?
totem itself prints this error message when started: (totem:5749): Gdk-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 399 error_code 8 request_code 153 (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.) Trace/breakpoint trap (core dumped) Additionally this does only happen on my system with NVidia graphics (and the nvidia driver): $ rpm -q -a \*nvidia\* kmod-nvidia-346.72-2.fc22.1.x86_64 xorg-x11-drv-nvidia-libs-346.72-1.fc22.i686 xorg-x11-drv-nvidia-kmodsrc-346.72-1.fc22.x86_64 kmod-nvidia-4.0.4-303.fc22.x86_64-346.72-2.fc22.1.x86_64 akmod-nvidia-346.72-2.fc22.1.x86_64 nvidia-texture-tools-2.0.8-9.fc22.x86_64 kmod-nvidia-4.0.4-301.fc22.x86_64-346.72-2.fc22.1.x86_64 xorg-x11-drv-nvidia-libs-346.72-1.fc22.x86_64 xorg-x11-drv-nvidia-346.72-1.fc22.x86_64 $ As a workaround it works for me to just run: $ CLUTTER_BACKEND=x11 totem
After digging a bit deeper (searching for NVIDIA issues with Gnome, I found the following: The same issue is reported for archlinux here: https://bugs.archlinux.org/task/44531 It is also pointing to https://bugzilla.gnome.org/show_bug.cgi?id=747489 finally.
Upstream has committed the fixes for this against the 1.22 branch. Could we either get a new stable release or the patches applied in the meantime?
Created attachment 1042830 [details] clutter package patches Both clutter and clutter-gtk need the upstream fixes. I've tested them and I can now view videos without passing CLUTTER_BACKEND=x11. I have sent a message to upstream requesting a new stable release. I have attached the upstream patches (configure.ac modified for our version) to apply to clutter in Fedora.
Created attachment 1042831 [details] clutter-gtk package patches I have attached the upstream patches (configure.ac modified for our version) to apply to clutter-gtk in Fedora. clutter-gtk needs to be rebuilt against the fixed clutter - new symbol.
Clutter 1.22.4 and Clutter-GTK 1.6.2 have been released today and they contain the fixes. May we get an update for those two?
(In reply to Michael Cronenworth from comment #20) > Clutter 1.22.4 and Clutter-GTK 1.6.2 have been released today and they > contain the fixes. May we get an update for those two? why don't you check koji (read: already built, you don't need to needinfo)
clutter-1.22.4-1.fc22,clutter-gtk-1.6.2-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/clutter-1.22.4-1.fc22,clutter-gtk-1.6.2-1.fc22
I cannot update with: sudo dnf update --enablerepo=updates-testing clutter
(In reply to Yajo from comment #23) > I cannot update with: sudo dnf update --enablerepo=updates-testing clutter Try again tomorrow, the update may have not made it to your local mirror yet
Package clutter-1.22.4-1.fc22, clutter-gtk-1.6.2-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing clutter-1.22.4-1.fc22 clutter-gtk-1.6.2-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-10997/clutter-1.22.4-1.fc22,clutter-gtk-1.6.2-1.fc22 then log in and leave karma (feedback).
clutter-1.22.4-1.fc22, clutter-gtk-1.6.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.