Version-Release number of selected component: easytag-2.1.10-1.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: easytag crash_function: gtk_window_present_with_time executable: /usr/bin/easytag kernel: 3.14.0-0.rc4.git1.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 gtk_window_present_with_time at gtkwindow.c:6793 #4 g_signal_emit_by_name at gsignal.c:3403 #5 g_application_impl_method_call at gapplicationimpl-dbus.c:195 #6 call_in_idle_cb at gdbusconnection.c:4875 #11 gtk_main at gtkmain.c:1257 #16 g_application_activate at gapplication.c:1905 #17 et_local_command_line at src/application.c:77 #18 g_application_run at gapplication.c:2083
Created attachment 869466 [details] File: backtrace
Created attachment 869467 [details] File: cgroup
Created attachment 869468 [details] File: core_backtrace
Created attachment 869469 [details] File: dso_list
Created attachment 869470 [details] File: environ
Created attachment 869471 [details] File: exploitable
Created attachment 869472 [details] File: limits
Created attachment 869473 [details] File: maps
Created attachment 869474 [details] File: open_fds
Created attachment 869475 [details] File: proc_pid_status
Created attachment 869476 [details] File: var_log_messages
Can reproduce.
I cannot seem to reproduce the crash with Rawhide updated as of today. The backtrace seem to show that EasyTAG was responding to the "activate" signal on GApplication, and presenting the main window, but that the window pointer was not valid. Could you provide steps to reproduce, so that I can try again to trigger the crash locally?
ho-ho. I can reproduce it many times ;) Steps to reproduce: 1. Open easytag 2. Press close button 3. Press "ESC" sometimes (until window will not close) 4. open new copy of easytag sample video of reproducing: http://ignatenkobrain.fedorapeople.org/rhbz1071563.ogv
Thanks for the information, and especially for the video! I have reproduced the crash locally and filed an upstream bug. I should be able to fix it either tonight (after GNOME releases are done) or tomorrow.
easytag-2.1.10-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/easytag-2.1.10-2.fc20
easytag-2.1.10-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/easytag-2.1.10-2.fc19
Package easytag-2.1.10-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing easytag-2.1.10-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-3441/easytag-2.1.10-2.fc20 then log in and leave karma (feedback).
easytag-2.1.10-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/easytag-2.1.10-3.fc20
easytag-2.1.10-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/easytag-2.1.10-3.fc19
easytag-2.1.10-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/easytag-2.1.10-4.fc19
easytag-2.1.10-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
easytag-2.1.10-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.