As far as I know, there is no easy way to get all the GConf entries which are used by certain binary/package. What collect_GConf does is that it tries to get the GConf subtree under /apps/binary-name, which works for many programs. (If it is not the case and the GConf contents are essential for fixing bugs, the package can provide its own hook to collect it.)

Not sure if that should be considered an error or not, though.

As Martin says, the proper fix would be to add a file called gnomeshell_event.conf into gnome-shell package containig somenthing like this:


(please note that "THE NAME OF THE DIR USED BY GS" has to be changed accordingly)
###

EVENT=collect_GConf analyzer=CCpp executable=gnome-shell dso_list~=.*/libgconf-2.*
        # assumption: gconftool-2 is present because libgconf is
        gconfdir="/apps/THE NAME OF THE DIR USED BY GS" &&
        {
                gconftool-2 --dir-exists=$gconfdir ||
                { echo "GConf directory $gconfdir does not exist"; exit 1; }
        } &&
        gconftool-2 --recursive-list $gconfdir >gconf_subtree &&
        echo "Element 'gconf_subtree' saved"

##

- and install it to the /etc/libreport/events.d/
- if you decide to do so, please add a dependency to pacakge libreport-filesystem, otherwise the top directories "libreport/events.d" might end-up unowned

(In reply to comment #2)
> As Martin says, the proper fix would be to add a file called
> gnomeshell_event.conf into gnome-shell package containing something like
> this:
Can this be used to report gnome-shell bugs as of today ?
I got a gnome-shell crash today and couldn't report it.

(In reply to comment #3)
> (In reply to comment #2)
> > As Martin says, the proper fix would be to add a file called
> > gnomeshell_event.conf into gnome-shell package containing something like
> > this:
> Can this be used to report gnome-shell bugs as of today ?
> I got a gnome-shell crash today and couldn't report it.

- should be, it depends if it was gnome-shell or the whole X what has crashed, but please create bz another ticket for it

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

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.