Bug 874731

Summary: [abrt] SDL_mixer-1.2.12-3.fc18: MikMod_Exit_internal: Process /usr/bin/playwave was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Aleksey <konovalov.aleks>
Component: SDL_mixerAssignee: Gwyn Ciesla <gwync>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dev, gwync, hdegoede, iprikryl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bb417be270da1dfa7b4c2ab8f85ca6d380eee2a5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:52:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: hb12.wav
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Aleksey 2012-11-08 18:18:54 UTC
Version-Release number of selected component:
SDL_mixer-1.2.12-3.fc18

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        playwave hb12.wav
crash_function: MikMod_Exit_internal
kernel:         3.6.6-3.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #5 MikMod_Exit_internal at ../playercode/mdriver.c:583
: #6 MikMod_Exit at ../playercode/mdriver.c:599
: #7 close_music at music.c:1520
: #8 Mix_CloseAudio at mixer.c:1135
: #9 CleanUp at playwave.c:282
: #11 pthread_join at pthread_join.c:92
: #12 SDL_SYS_WaitThread at src/thread/pthread/SDL_systhread.c:107
: #13 SDL_WaitThread at src/thread/SDL_thread.c:272
: #14 SDL_AudioQuit at src/audio/SDL_audio.c:629
: #15 SDL_QuitSubSystem at src/SDL.c:190

Comment 1 Aleksey 2012-11-08 18:18:57 UTC
Created attachment 641001 [details]
File: core_backtrace

Comment 2 Aleksey 2012-11-08 18:18:59 UTC
Created attachment 641002 [details]
File: environ

Comment 3 Aleksey 2012-11-08 18:19:01 UTC
Created attachment 641003 [details]
File: hb12.wav

Comment 4 Aleksey 2012-11-08 18:19:03 UTC
Created attachment 641004 [details]
File: backtrace

Comment 5 Aleksey 2012-11-08 18:19:05 UTC
Created attachment 641005 [details]
File: limits

Comment 6 Aleksey 2012-11-08 18:19:07 UTC
Created attachment 641006 [details]
File: cgroup

Comment 7 Aleksey 2012-11-08 18:19:09 UTC
Created attachment 641008 [details]
File: executable

Comment 8 Aleksey 2012-11-08 18:19:12 UTC
Created attachment 641010 [details]
File: maps

Comment 9 Aleksey 2012-11-08 18:19:14 UTC
Created attachment 641012 [details]
File: dso_list

Comment 10 Aleksey 2012-11-08 18:19:16 UTC
Created attachment 641014 [details]
File: proc_pid_status

Comment 11 Aleksey 2012-11-08 18:19:20 UTC
Created attachment 641017 [details]
File: var_log_messages

Comment 12 Aleksey 2012-11-08 18:19:32 UTC
Created attachment 641019 [details]
File: open_fds

Comment 13 Scott Dowdle 2012-12-07 18:56:25 UTC
I think there is something hinky with the SDL_mixer-1.2.12-3.fc18.x86_64 package.  When it is installed it says:

/sbin/ldconfig: File /lib64/lib_SDL_net-1.2.so.0.8.0 is empty, not checked

It says that for a few other files too (libmikmod, libSDL_net, libmikmod.so.3).

I'm guessing it is a bad package build that slipped through?

Comment 14 Gwyn Ciesla 2012-12-07 18:57:28 UTC
Can you post the full output?

Comment 15 Scott Dowdle 2012-12-07 19:17:36 UTC
Nevermind.  Turns out I had three packages that failed verification (SDL_mixer, SDL_net, and libmikmod) because the library files they provided were 0 bytes in size.

I manually downloaded the packages and did an rpm -ivh --force on them... and then verified them again and they were fine.

I'm guessing the issue was caused by a bad or aborted prelink run... and not a back package build.  Sorry.  Made you look. :)

Comment 16 Gwyn Ciesla 2012-12-07 19:21:23 UTC
:)  Did it resolve the crash?

Comment 17 Fedora End Of Life 2013-12-21 15:11:32 UTC
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.

Comment 18 Fedora End Of Life 2014-02-05 22:52:33 UTC
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.