Description of problem: I was trying to adjust the volume. Version-Release number of selected component: volumeicon-0.4.6-4.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: volumeicon crash_function: asound_set_volume executable: /usr/bin/volumeicon kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 asound_set_volume at alsa_backend.c:209 #5 status_icon_on_button_release at volumeicon.c:577 #6 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #11 gtk_status_icon_button_release at gtkstatusicon.c:1798 #12 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #17 gtk_widget_event_internal at gtkwidget.c:5017 #18 gtk_widget_event at gtkwidget.c:4814 #19 gtk_propagate_event at gtkmain.c:2490 #20 gtk_main_do_event at gtkmain.c:1685 #26 gtk_main at gtkmain.c:1257 Potential duplicate: bug 879449
Created attachment 897273 [details] File: backtrace
Created attachment 897274 [details] File: cgroup
Created attachment 897275 [details] File: core_backtrace
Created attachment 897276 [details] File: dso_list
Created attachment 897277 [details] File: environ
Created attachment 897278 [details] File: limits
Created attachment 897279 [details] File: maps
Created attachment 897280 [details] File: open_fds
Created attachment 897281 [details] File: proc_pid_status
Created attachment 897282 [details] File: var_log_messages
Another user experienced a similar problem: I added the updates and was alerted by notification icon that I needed to updated particularly a audio setting through veromix... I did so, and upon restart, downloaded a few packages from the repository... one of those was a audio beat maker synth, when I used that or began to tinker with the software it automatically set or parsed my audio settings and from then on I have had 3 volume icons. I am more familiar with pulseaudio but not sure if what I am describing is the cause... I am very concerned about the integrity of my system, and have done some digging and poking around to discover that my bios have been compromised for sometime, for about a year maybe less... I would like to also find some external help from fedora security to secure this desktop, and any leads in the right direction will be included overall in my references to recommended secure distros, no matter if any external advice is given, or this issue can be directly or indirectly assisted/solved. I hope what little I have given on step by step info regarding this issue has been somewhat of an indicator, or a small piece of a larger vunerability... I'll be in the forums and chats with my well analyzed and versed issues very soon, and thanks very much Fedora Team! ...For all you guys do! reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/volumeicon crash_function: asound_set_volume executable: /usr/bin/volumeicon kernel: 3.16.6-200.fc20.x86_64 package: volumeicon-0.4.6-4.fc20 reason: volumeicon killed by SIGABRT runlevel: N 5 type: CCpp uid: 1024
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.