Description of problem: Just tried to open pavucontrol, nothing showed. Version-Release number of selected component: pavucontrol-2.0-4.fc21 Additional info: reporter: libreport-2.2.1 backtrace_rating: 3 cmdline: pavucontrol crash_function: strcmp executable: /usr/bin/pavucontrol kernel: 3.15.0-0.rc1.git1.2.fc21.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 strcmp at /lib/libc.so.6 #1 ?? #2 MainWindow::updateCard(pa_card_info const&) #3 context_get_card_info_callback at /lib/libpulse.so.0 #4 run_action at /usr/lib/pulseaudio/libpulsecommon-5.0.so #5 pa_pdispatch_run at /usr/lib/pulseaudio/libpulsecommon-5.0.so #6 pstream_packet_callback at /lib/libpulse.so.0 #7 do_pstream_read_write at /usr/lib/pulseaudio/libpulsecommon-5.0.so #8 callback at /usr/lib/pulseaudio/libpulsecommon-5.0.so #9 dispatch_func at /lib/libpulse-mainloop-glib.so.0
Created attachment 887224 [details] File: backtrace
Created attachment 887225 [details] File: cgroup
Created attachment 887226 [details] File: core_backtrace
Created attachment 887227 [details] File: dso_list
Created attachment 887228 [details] File: environ
Created attachment 887229 [details] File: exploitable
Created attachment 887230 [details] File: limits
Created attachment 887231 [details] File: maps
Created attachment 887232 [details] File: open_fds
Created attachment 887233 [details] File: proc_pid_status
Created attachment 887234 [details] File: var_log_messages
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.