smolt profile is a bit of information potentially useful in determining why some program is crashing. However, it can only be collected if smolt is installed. We (abrt/libreport team) currently do this in a somewhat ugly way in /etc/libreport/events.d/smolt_event.conf file: EVENT=collect_Smolt which smoltSendProfile >/dev/null 2>&1 || { echo "Smolt package not installed, can't save profile" exit 0 } smoltSendProfile -p >smolt_data 2>&1 || exit $? echo "Smolt profile successfully saved" Basically, it is "if smoltSendProfile is installed, then run it". This is stupid: the Fedora machine KNOWS (via rpm database) when smolt is installed. IOW: the more elegand way is to install this file as part of smolt, not as part of libreport. For now we maintain this file as a part of libreport packages, but we feel this mechanism has proved to be working well and it is time to move it to the smolt package. If you want to adopt this, make it so that your package(s) install your own /etc/libreport/events.d/smolt_event.conf. After you did this, ping us and we will remove our file. In order to make sure /etc/libreport/events.d/ directory has a proper package ownership, we are going to create libreport-fs package which creates it. You can ensure the directory is created by making your package dependent on libreport-fs.
Just a note: the package which creates /etc/libreport/events.d/ will be called libreport-filesystem. It is already in libreport git, and will be in Fedora with next release (a week or two).
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.