Version-Release number of selected component: gnome-tweak-tool-3.9.91-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: python /usr/bin/gnome-tweak-tool crash_function: sem_post executable: /usr/bin/python2.7 kernel: 3.11.0-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 sem_post at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_post.S:33 #1 PyThread_release_lock at /usr/src/debug/Python-2.7.5/Python/thread_pthread.h:349 #2 g_object_ref at gobject.c:3069 #3 g_settings_backend_dispatch_signal at gsettingsbackend.c:329 #4 g_settings_backend_changed at gsettingsbackend.c:400 #5 dconf_engine_change_notify at dconfsettingsbackend.c:250 #6 dconf_engine_handle_dbus_signal at dconf-engine.c:1164 #7 emit_signal_instance_in_idle_cb at gdbusconnection.c:3743 #11 g_main_context_iteration at gmain.c:3773 #12 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:81
Created attachment 797671 [details] File: backtrace
Created attachment 797672 [details] File: cgroup
Created attachment 797673 [details] File: core_backtrace
Created attachment 797674 [details] File: dso_list
Created attachment 797675 [details] File: environ
Created attachment 797676 [details] File: exploitable
Created attachment 797677 [details] File: limits
Created attachment 797678 [details] File: maps
Created attachment 797679 [details] File: open_fds
Created attachment 797680 [details] File: proc_pid_status
have this bug too.
I was enabling extension and crashed same bug happened.
Seen this too. Didn't do much with tweak tool. gnome-tweak-tool-3.9.91-1.fc20.noarch
Still seeing this as well. gnome-tweak-tool-3.10.0-1.fc20.noarch Occurred while modifying a setting in a Gnome-shell extension.
Same issue with gnome-tweak-tool-3.10.0-1.fc20.noarch
I see this bug when I leave gnome-tweak-tool open for a long time (and don't touch it at all).
This one has now been fixed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=709223 Not sure when the changes will be pushed to f20.
(In reply to Ryan Lerch from comment #17) > This one has now been fixed upstream: > https://bugzilla.gnome.org/show_bug.cgi?id=709223 > > Not sure when the changes will be pushed to f20. will be on 3.10.1+ versions
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.