Hide Forgot
Description of problem: Not clear just how this happened, but it appeared to be coincident with the first time I booted kernel 3.11.10 Sound preferences crashes, no sound at all from anything. The GNOME volume control is still there and can be adjusted, and pressing the + and - volume buttons on the Thinkpad (T520) bring up the speaker image with the level bar beneath it as usual, but no sound. The same yum update that brought in the kernel also included: subversion-libs-1.7.14-1 sane-backends-libs-1.0.24-7 sane-backends-1.0.24-7 subversion-1.7.14-1 ghostscript-9.06-8 ghostscript-cups-9.06-8. subversion-javahl-1.7.14 sane-backends-drivers-scanners-1.0.24-7 flash-plugin-11.2.202.332 seamonkey-2.22.1-1 ibus-typing-booster-1.2.7-1 python-BeautifulSoup-3.2.1-7 armadillo-3.920.3-1 sane-backends-doc-1.0.24-7 At around the same time, several GNOME desktop extensions stopped working but were restored with gnome-tweak-tool. It seems possible that some configuration file was corrupted Version-Release number of selected component: control-center-3.6.3-2.fc18 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gnome-control-center sound crash_function: g_vasprintf executable: /usr/bin/gnome-control-center kernel: 3.11.10-100.fc18.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_vasprintf at /lib64/libglib-2.0.so.0 #3 g_strdup_vprintf at /lib64/libglib-2.0.so.0 #6 gvc_mixer_control_lookup_device_from_stream at /usr/lib64/control-center-1/panels/libsound.so #7 gvc_mixer_control_set_default_source at /usr/lib64/control-center-1/panels/libsound.so #8 gvc_mixer_control_change_input at /usr/lib64/control-center-1/panels/libsound.so #9 on_input_selection_changed at /usr/lib64/control-center-1/panels/libsound.so #10 _g_closure_invoke_va at /lib64/libgobject-2.0.so.0 #13 gtk_tree_selection_select_path at /lib64/libgtk-3.so.0 #14 gtk_tree_selection_select_iter at /lib64/libgtk-3.so.0 #15 on_control_active_input_update at /usr/lib64/control-center-1/panels/libsound.so
Created attachment 835997 [details] File: backtrace
Created attachment 835998 [details] File: cgroup
Created attachment 835999 [details] File: core_backtrace
Created attachment 836000 [details] File: dso_list
Created attachment 836001 [details] File: environ
Created attachment 836002 [details] File: exploitable
Created attachment 836003 [details] File: limits
Created attachment 836004 [details] File: maps
Created attachment 836005 [details] File: open_fds
Created attachment 836006 [details] File: proc_pid_status
Created attachment 836007 [details] File: var_log_messages
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.