Version-Release number of selected component: qashctl-0.17.2-3.fc22 Additional info: reporter: libreport-2.6.1 backtrace_rating: 4 cmdline: qashctl crash_function: arcam_av_close executable: /usr/bin/qashctl global_pid: 23093 kernel: 4.0.8-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 arcam_av_close at ctl_arcam_av.c:144 #1 _snd_ctl_arcam_av_open at ctl_arcam_av.c:980 #2 snd_ctl_open_conf at control.c:930 #3 snd_ctl_open_noupdate at control.c:957 #4 snd_ctl_open at control.c:976 #5 snd_hctl_open at hcontrol.c:75 #6 QSnd::Mixer_HCTL::open at /usr/src/debug/qastools_0.17.2/shared/src/qsnd/mixer_hctl.cpp:115 #7 Views::Mixer_HCTL::set_mdev_setup at /usr/src/debug/qastools_0.17.2/qashctl/src/views/mixer_hctl.cpp:168 #8 QObject::event at kernel/qobject.cpp:1222 #9 QWidget::event at kernel/qwidget.cpp:8859 Potential duplicate: bug 1099635
Created attachment 1056074 [details] File: backtrace
Created attachment 1056075 [details] File: cgroup
Created attachment 1056076 [details] File: core_backtrace
Created attachment 1056077 [details] File: dso_list
Created attachment 1056078 [details] File: environ
Created attachment 1056079 [details] File: limits
Created attachment 1056080 [details] File: maps
Created attachment 1056081 [details] File: mountinfo
Created attachment 1056082 [details] File: namespaces
Created attachment 1056083 [details] File: open_fds
Created attachment 1056084 [details] File: proc_pid_status
Created attachment 1056085 [details] File: var_log_messages
Have you been able to reproduce this crash?
Lessee, that was 3 months ago ... I recall opening QasHctl, and it crashing; I seem to recall trying to open it a couple of times with the same result. However, I didn't remove it, so I just opened QasHctl again just now and it opened set to Mixer device "default". BUT, when I select Mixer device "arcam_av", it crashed ... whether it's the same or not, I can't tell at a glance. I reopened it and selected "hw: card", and it's still open. It only crashes when I select "arcam_av". FWIW, at the time this was filed, I had a CreativeLabs Audigy 2 card; I've since replaced it with an Asus Xonar DSX. However, I'm also having receiver problems and am not getting any sound at present.
Ok, I have posted to the upstream devel mailing list to ask them to take a look. We'll see what happens.
Answer from upstream: https://sourceforge.net/p/qastools/mailman/message/34593996/ Basically, he things it's an alsa driver bug, not a direct bug in qastools...
Let me know if there's anything else I can do but for now...
Given the situation, I can accept that ... much appreciated, and thank you for the follow up!