Hide Forgot
Version-Release number of selected component: love-0.8.0-4.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: love /usr/share/mari0/mari0.love crash_function: aluMixData executable: /usr/bin/love kernel: 3.11.6-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #1 aluMixData at /usr/src/debug/openal-soft-1.15.1/Alc/ALu.c:987 #2 PulseProc at /usr/src/debug/openal-soft-1.15.1/Alc/backends/pulseaudio.c:846 #3 StarterFunc at /usr/src/debug/openal-soft-1.15.1/Alc/alcThread.c:96 Potential duplicate: bug 922431
Created attachment 819312 [details] File: backtrace
Created attachment 819313 [details] File: cgroup
Created attachment 819314 [details] File: core_backtrace
Created attachment 819315 [details] File: dso_list
Created attachment 819316 [details] File: environ
Created attachment 819317 [details] File: exploitable
Created attachment 819318 [details] File: limits
Created attachment 819319 [details] File: maps
Created attachment 819320 [details] File: open_fds
Created attachment 819321 [details] File: proc_pid_status
Created attachment 819322 [details] File: var_log_messages
*** Bug 922431 has been marked as a duplicate of this bug. ***
openal is known to cause issues on love. Upstream is looking into fixing this by switching audio libraries
Cant you reproduce this on love 0.9.0 (in updates-testing)?
Please let me know if this still happens in 0.9.0 and how to reproduce it if possible
Sorry, I have not installed this package, I don't use them now.
I can't reproduce this, closing for now.
Can this bug accept new info from a different distro altogether?