Description of problem: On Login after reboot after an update (fedora-update repo; not update-testing) [fedora 18 beta lxde live iso installation]->[head version] rebooted. External sound card Creative X-Fi HD connected (might be a problem for pm-mixer). (Reproduction not tested. Version-Release number of selected component: pnmixer-0.5.1-4.fc18 Additional info: backtrace_rating: 4 cmdline: pnmixer crash_function: snd_mixer_detach executable: /usr/bin/pnmixer kernel: 3.6.10-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (6 frames) #0 snd_mixer_detach at mixer.c:254 #1 close_mixer at alsa.c:195 #2 get_channels at alsa.c:221 #3 get_cards at alsa.c:79 #4 alsaset at alsa.c:244 #5 alsa_init at alsa.c:350
Created attachment 675754 [details] File: backtrace
Created attachment 675755 [details] File: cgroup
Created attachment 675756 [details] File: core_backtrace
Created attachment 675757 [details] File: dso_list
Created attachment 675758 [details] File: environ
Created attachment 675759 [details] File: limits
Created attachment 675760 [details] File: maps
Created attachment 675761 [details] File: open_fds
Created attachment 675762 [details] File: proc_pid_status
Created attachment 675763 [details] File: var_log_messages
Greetings. I have an unusual problem with pnmixer. When I start the system up, it works fine. But if more than one user logs into the system (at all, they don't have to log in at the same time) pnmixer quits and sound stops working unless the application using sound is run with root privileges. Restarting pnmixer fails with a segmentation fault unless it is run as root. Even when run as root, all applications need to be run as root in order to use sound. Rebooting solves the problem but only until a second user logs into the system. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: pnmixer crash_function: snd_mixer_detach executable: /usr/bin/pnmixer kernel: 3.9.4-200.fc18.i686 package: pnmixer-0.5.1-4.fc18 reason: Process /usr/bin/pnmixer was killed by signal 11 (SIGSEGV) reported_to: uReport: BTHASH=58d646b123afd593a4a84ab97ecb6be5bc0b89db runlevel: N 5 uid: 1000 xsession_errors: abrt-applet: repeated problem in pnmixer-0.5.1-4.fc18, not showing the notification
Got this on booting with kernel3.9.11-200.fc18.x86_64 and pnmixer-0.5.1-4.fc18.x86_64
*** Bug 995859 has been marked as a duplicate of this bug. ***
(In reply to i-tek from comment #0) > External sound card Creative X-Fi HD connected (might be a problem > for pm-mixer). Yes, AFAICS this only happens with more than one soundcard. Can you please try unplugging the card?
I get this after trying to follow https://docs.fedoraproject.org/en-US/Fedora/18/html/Musicians_Guide/sect-Musicians_Guide-Integrating_PulseAudio_with_JACK.html . Patch is as follows, default.pa.std is installed version of default.pa: "[jones@localhost pulse]$ diff -c default.pa.std default.pa *** default.pa.std 2013-02-18 17:03:39.000000000 -0500 --- default.pa 2013-12-13 23:22:01.960317414 -0500 *************** *** 42,47 **** --- 42,51 ---- ### (it's probably better to not load these drivers manually, but instead ### use module-udev-detect -- see below -- for doing this automatically) #load-module module-alsa-sink + ###Per https://docs.fedoraproject.org/en-US/Fedora/18/html/Musicians_Guide/sect-Musicians_Guide-Integrating_PulseAudio_with_JACK.html: + ###Add the following lines, underneath the line that says [code]#load-module module-alsa-sink[/code]: + load-module module-jack-sink + load-module module-jack-source #load-module module-alsa-source device=hw:1,0 #load-module module-oss device="/dev/dsp" sink_name=output source_name=input #load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input " I found the following in /var/log/messages: "Dec 13 23:29:00 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server socket err = No such file or directory< Dec 13 23:29:00 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server request channel< Dec 13 23:29:00 localhost blueman-mechanism: loading Network Dec 13 23:29:00 localhost abrt-hook-ccpp[2473]: Saved core dump of pid 2270 (/usr/bin/pnmixer) to /var/tmp/abrt/ccpp-2013-12-13-23:28:59-2270 (11051008 bytes) Dec 13 23:29:01 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server socket err = No such file or directory< Dec 13 23:29:01 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server request channel< Dec 13 23:29:01 localhost abrt-server[2484]: Generating core_backtrace Dec 13 23:29:01 localhost abrt-server[2484]: Generating backtrace Dec 13 23:29:02 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server socket err = No such file or directory< Dec 13 23:29:02 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server request channel< Dec 13 23:29:03 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server socket err = No such file or directory< Dec 13 23:29:03 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server request channel< Dec 13 23:29:04 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server socket err = No such file or directory< Dec 13 23:29:04 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server request channel< Dec 13 23:29:04 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server request channel< Dec 13 23:29:05 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server socket err = No such file or directory< Dec 13 23:29:05 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >Cannot connect to server request channel< Dec 13 23:29:06 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: JACK error >jack server is not running or cannot be started< Dec 13 23:29:06 localhost pulseaudio[2471]: [pulseaudio] module-jack-sink.c: jack_client_open() failed. Dec 13 23:29:06 localhost pulseaudio[2471]: [pulseaudio] module.c: Failed to load module "module-jack-sink" (argument: ""): initialization failed. Dec 13 23:29:06 localhost pulseaudio[2471]: [pulseaudio] main.c: Module load failed. Dec 13 23:29:06 localhost pulseaudio[2471]: [pulseaudio] main.c: Failed to initialize daemon. Dec 13 23:29:06 localhost pulseaudio[2463]: [pulseaudio] main.c: Daemon startup failed. Dec 13 23:29:08 localhost abrt-server[2484]: journalctl: unrecognized option '--system' Dec 13 23:29:08 localhost abrt-server[2484]: Duplicate: core backtrace Dec 13 23:29:08 localhost abrt-server[2484]: DUP_OF_DIR: /var/tmp/abrt/ccpp-2013-12-13-23:17:21-1458 Dec 13 23:29:08 localhost abrt-server[2484]: Deleting problem directory ccpp-2013-12-13-23:28:59-2270 (dup of ccpp-2013-12-13-23:17:21-1458) " I also notice a potential problem with pulseaudio version numbers: "yum list 'pulseaudio-*' Loaded plugins: changelog, fastestmirror, langpacks, presto, refresh-packagekit, security http://dl.atrpms.net/f18-x86_64/atrpms/stable/repodata/repomd.xml: [Errno 14] curl#7 - "couldn't connect to host" Trying other mirror. Loading mirror speeds from cached hostfile * fedora: mirror.nexcess.net * rpmfusion-free: mirror.nexcess.net * rpmfusion-free-updates: mirror.nexcess.net * rpmfusion-nonfree: mirror.nexcess.net * rpmfusion-nonfree-updates: mirror.nexcess.net * updates: mirror.nexcess.net Installed Packages pulseaudio.x86_64 2.1-7.fc18 @/pulseaudio-2.1-7.fc18.x86_64 pulseaudio-gdm-hooks.x86_64 2.1-6.fc18 @/pulseaudio-gdm-hooks-2.1-6.fc18.x86_64 pulseaudio-libs.i686 2.1-7.fc18 @/pulseaudio-libs-2.1-7.fc18.i686 pulseaudio-libs.x86_64 2.1-7.fc18 @/pulseaudio-libs-2.1-7.fc18.x86_64 pulseaudio-libs-glib2.x86_64 2.1-7.fc18 @/pulseaudio-libs-glib2-2.1-7.fc18.x86_64 pulseaudio-module-bluetooth.x86_64 2.1-7.fc18 @/pulseaudio-module-bluetooth-2.1-7.fc18.x86_64 pulseaudio-module-jack.x86_64 2.1-7.fc18 @/pulseaudio-module-jack-2.1-7.fc18.x86_64 pulseaudio-module-x11.x86_64 2.1-7.fc18 @/pulseaudio-module-x11-2.1-7.fc18.x86_64 pulseaudio-utils.x86_64 2.1-7.fc18 @/pulseaudio-utils-2.1-7.fc18.x86_64 Available Packages pulseaudio-equalizer.noarch 2.7-10.fc18 fedora pulseaudio-esound-compat.x86_64 2.1-6.fc18 updates pulseaudio-libs-devel.i686 2.1-6.fc18 updates pulseaudio-libs-devel.x86_64 2.1-6.fc18 updates pulseaudio-libs-glib2.i686 2.1-6.fc18 updates pulseaudio-module-gconf.x86_64 2.1-6.fc18 updates pulseaudio-module-lirc.x86_64 2.1-6.fc18 updates pulseaudio-module-zeroconf.x86_64 2.1-6.fc18 updates pulseaudio-utils.i686 2.1-6.fc18 updates " In other words, yum is proposing 2.1-6 for pulseaudio-module-*, although pulseaudio is at 2.1-7.
After undoing the patch to default.pa, the aborts have stopped, and the volume control icon appears again.
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.