Description of problem: brasero-2.31.92-1.fc15.x86_64 core dumps.... Appears to be an issue with both gtk2 and gtk3 simultaneously..... gdb says: Core was generated by `brasero'. Program terminated with signal 5, Trace/breakpoint trap. #0 g_logv (log_domain=0x7feb1b600d1b "Gtk", log_level=<value optimized out>, format=0x7feb1b68da80 "GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported", args1=0x7fffc01c1100) at gmessages.c:563 563 g_private_set (g_log_depth, GUINT_TO_POINTER (depth)); (gdb) set pagination off (gdb) bt full #0 g_logv (log_domain=0x7feb1b600d1b "Gtk", log_level=<value optimized out>, format=0x7feb1b68da80 "GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported", args1=0x7fffc01c1100) at gmessages.c:563 depth = 0 domain = 0x0 data = 0x0 log_func = 0x7feb187736b0 <g_log_default_handler> domain_fatal_mask = <value optimized out> masquerade_fatal = <value optimized out> test_level = <value optimized out> was_fatal = 0 was_recursion = 0 i = 2 #1 0x00007feb18774603 in g_log (log_domain=<value optimized out>, log_level=<value optimized out>, format=<value optimized out>) at gmessages.c:577 args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7fffc01c11e0, reg_save_area = 0x7fffc01c1120}} #2 0x00007feb1b4a8560 in check_mixed_deps (context=<value optimized out>, group=<value optimized out>, data=<value optimized out>, error=<value optimized out>) at gtkmain.c:714 module = 0x1c824f0 func = 0x7feb1ad74680 #3 do_pre_parse_initialization (context=<value optimized out>, group=<value optimized out>, data=<value optimized out>, error=<value optimized out>) at gtkmain.c:731 env_string = <value optimized out> #4 pre_parse_hook (context=<value optimized out>, group=<value optimized out>, data=<value optimized out>, error=<value optimized out>) at gtkmain.c:839 No locals. #5 0x00007feb18778360 in g_option_context_parse (context=0x1c80f70, argc=0x7fffc01c134c, argv=0x7fffc01c1340, error=0x7fffc01c12f8) at goption.c:1738 i = <value optimized out> j = <value optimized out> k = <value optimized out> list = 0x0 #6 0x00007feb1b4a8f40 in gtk_parse_args (argc=0x7fffc01c134c, argv=0x7fffc01c1340) at gtkmain.c:1031 option_context = 0x1c80f70 gtk_group = <value optimized out> error = 0x0 #7 0x00007feb1b4a8f99 in gtk_init_check (argc=<value optimized out>, argv=<value optimized out>) at gtkmain.c:1067 No locals. #8 0x00007feb1b4a8fc9 in gtk_init (argc=<value optimized out>, argv=<value optimized out>) at gtkmain.c:1114 No locals. #9 0x000000000041f474 in main (argc=1, argv=0x7fffc01c1448) at main.c:82 uapp = 0x0 context = <value optimized out> (gdb) Version-Release number of selected component (if applicable): brasero-2.31.92-1.fc15.x86_64 How reproducible: Every time.... Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Continue to get this with brasero-2.32.0-1.fc15.x86_64: Sep 28 10:17:16 tlondon kernel: brasero[19064] trap int3 ip:7f19acdaa279 sp:7fffb331f020 error:0 Sep 28 10:17:16 tlondon abrt[19065]: saved core dump of pid 19064 to /home/tbl/core.19064 (1929216 bytes) Here is what I get when I run from a terminal window: [tbl@tlondon ~]$ brasero Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported aborting... Trace/breakpoint trap (core dumped) [tbl@tlondon ~]$
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.