Version-Release number of selected component: control-center-3.11.91-1.fc21 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: __pthread_mutex_lock executable: /usr/bin/gnome-control-center kernel: 3.14.0-0.rc5.git2.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:66 #1 crLockMutex at /usr/src/debug/VirtualBox-4.3.6/src/VBox/GuestHost/OpenGL/util/threads.c:166 #2 crHashtableLock at /usr/src/debug/VirtualBox-4.3.6/src/VBox/GuestHost/OpenGL/util/hash.c:434 #3 stubSyncThreadProc at /usr/src/debug/VirtualBox-4.3.6/src/VBox/Additions/common/crOpenGL/load.c:898 #4 rtThreadMain at /usr/src/debug/VirtualBox-4.3.6/src/VBox/Runtime/common/misc/thread.cpp:712 #5 rtThreadNativeMain at /usr/src/debug/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
Created attachment 872952 [details] File: backtrace
Created attachment 872953 [details] File: cgroup
Created attachment 872954 [details] File: core_backtrace
Created attachment 872955 [details] File: dso_list
Created attachment 872956 [details] File: environ
Created attachment 872957 [details] File: exploitable
Created attachment 872958 [details] File: limits
Created attachment 872959 [details] File: maps
Created attachment 872960 [details] File: open_fds
Created attachment 872961 [details] File: proc_pid_status
Created attachment 872962 [details] File: var_log_messages
I just experienced this as well, after having the gnome-control-center (Settings >> Networking) open simultaneously on the Virtual desktop and on the Host system.
Problem persists upon reboots.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.