GNOME Bugzilla – Bug 611343
X11 error attempting to play a mp4 file
Last modified: 2018-09-21 16:59:40 UTC
Original report: http://bugs.debian.org/568199 by Adam Majer. Perfectly reproducible with brasero 2.28.3, while totem works fine. 1. add mp4 file for burning 2. click on it 3. attempt to play it from within brasero ======= (brasero:27196): Gtk-CRITICAL **: gtk_box_pack: assertion `child->parent == NULL' failed ** (brasero:27196): WARNING **: Failed to inhibit the system from suspending: The name org.gnome.SessionManager was not provided by any .service files ** (brasero:27196): WARNING **: Failed to restore the system power manager: The name org.gnome.SessionManager was not provided by any .service files (brasero:27196): Gtk-WARNING **: Attempting to add a widget with type GtkHBox to a GtkAlignment, but as a GtkBin subclass a GtkAlignment can only contain one widget at a time; it already contains a widget of type GtkButton (brasero:27196): Gtk-CRITICAL **: gtk_box_pack: assertion `child->parent == NULL' failed The program 'brasero' received an X Window System error. This probably reflects a bug in the program. The error was 'BadIDChoice (invalid resource ID chosen for this connection)'. (Details: serial 239886 error_code 14 request_code 1 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 can't reproduce this bug using git master. Can you get a backtrace please ?
Long backtrace is long. Breakpoint 1, gdk_x_error (display=0x6af3f0, error=0x7fffffffb1f0) at /build/buildd-gtk+2.0_2.18.9-2-amd64-8Xyr17/gtk+2.0-2.18.9/gdk/x11/gdkmain-x11.c:438 in /build/buildd-gtk+2.0_2.18.9-2-amd64-8Xyr17/gtk+2.0-2.18.9/gdk/x11/gdkmain-x11.c (gdb) thread apply all bt full
+ Trace 221102
Thread 1 (Thread 0x7ffff7fc37d0 (LWP 18068))
Hi Josselin, if you have time, could you please check again whether this issue still happens in Brasero 3.2 or 3.0 and update this report by adding a comment and changing the "Version" field and provide information about your distribution? Thanks a lot.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/95.