Version-Release number of selected component: volumeicon-0.4.6-2.fc18 Additional info: backtrace_rating: 4 cmdline: volumeicon crash_function: asound_get_volume executable: /usr/bin/volumeicon kernel: 3.7.9-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #4 asound_get_volume at alsa_backend.c:86 Potential duplicate: bug 725613
Created attachment 703957 [details] File: backtrace
Created attachment 703958 [details] File: build_ids
Created attachment 703959 [details] File: cgroup
Created attachment 703960 [details] File: core_backtrace
Created attachment 703961 [details] File: environ
Created attachment 703962 [details] File: limits
Created attachment 703963 [details] File: maps
Created attachment 703964 [details] File: open_fds
Created attachment 703965 [details] File: proc_pid_status
Created attachment 703966 [details] File: smolt_data
startx then it crashed as it started up backtrace_rating: 4 Package: volumeicon-0.4.6-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
Thanks for submitting this crash report. Balint, what did you do to make the volumeicon crash? Kerry, does it crash every time you run startx? How do you handle device permissions, are you wrapping your session in ck-launch-session? Do you run pulseaudio? And does any of you have more than one soundcard or anything special like an external USB soundcard?
I didn't do anything. I installed a 'pure' Fedora 17 with XFCE and upgrade to 18. That's it. After the upgrade the volume icon disappeared. Nowdays I use 'Audio Mixer Plugin' to manage volume. I know, you didn't ask from me, but I use pulseaudio. I think it is the default install.
I think it crashes every time I startx. I don't restart very often through, but it does seem like one of the normal steps I encounter seeing the crash report. I'm not actually really sure what volumeicon does or why it is being started. It isn't anything that I've specifically set to start. I seem to remember getting these crashes for a number of releases back. Yes, pulseaudio is running. I believe my session is started by whatever got configured by 'switchdesk kde'. Also, I don't think I've done anything to my device permissions. I know every six months or so (going back many many releases), sound stops working and I have to fiddle around with lots of things to get it back on (usually a combination of switching things around in alsamixer then pavucontrol).
right after xfce login backtrace_rating: 4 cmdline: volumeicon crash_function: asound_get_volume executable: /usr/bin/volumeicon kernel: 3.8.5-201.fc18.x86_64 package: volumeicon-0.4.6-2.fc18 reason: Process /usr/bin/volumeicon was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 2 xsession_errors: volumeicon: alsa_backend.c:86: asound_get_volume: Assertion `m_elem != ((void *)0)' failed.
*** Bug 913163 has been marked as a duplicate of this bug. ***
*** Bug 928470 has been marked as a duplicate of this bug. ***
*** Bug 879449 has been marked as a duplicate of this bug. ***
Still happens with volumeicon-0.4.6-3.fc19.x86_64, FC19 Aug 4 16:03:44 XXXX /etc/gdm/Xsession[1227]: volumeicon: alsa_backend.c:86: asound_get_volume: Assertion `m_elem != ((void *)0)' failed.
*** Bug 976970 has been marked as a duplicate of this bug. ***
*** Bug 988586 has been marked as a duplicate of this bug. ***
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.