Red Hat Bugzilla – Bug 748744
libreport won't send Smolt report unless it was a generated already
Last modified: 2013-03-07 21:12:37 EST
Description of problem:
I started F-16 RC-TC2 compose and tried to report a bug. I selected Smolt profile to be send, however when the time for Smolt profile generation came libreport just claimed Smolt exited with code 9. Since this is LiveCD, Smolt profile wasn't generated yet and if you try to generate as a user it fails with the very same exit code 9 (tested in terminal with `smoltSendProfile').
libreport should probably verify that profile was generated already (and thus can be "re-generated"/send by libreport), or executed as user capable of Smolt profile generation (currently only root, I guess).
Version-Release number of selected component (if applicable):
I can generate the smolt profile as non-root, this must have been a different problem, can you still reproduce it?
Is /etc/smolt/hw-uuid present on that system already? If so then `smoltSendProfile' was ran by root in the past, because mentioned file is ghost file (see smolt.spec) which is not created by the smolt RPM.
The best way to test it is by F-16 RC5 Desktop LiveCD <http://serverbeach1.fedoraproject.org/pub/alt/stage/16.RC5/Live/x86_64/>. Right after start, report crash, check smolt profile generation -- which fails with exit code == 9.
If you run `smoltSendProfile -p' in terminal you'll get "Unable to save UUID to /etc/smolt/hw-uuid. Please run once as root." and exit code 9.
Seems more like problem with smolt - it should create the file somewhere else if it's not run with root privs.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.
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 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 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 to click on
"Clone This Bug" and open it against that version of Fedora.
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.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.
Thank you for reporting this bug and we are sorry it could not be fixed.