In last two weeks these components were crashing the most on Fedora 20:
1. gnome-shell seen 12370 times (23% of all reports) http://retrace.fedoraproject.org/faf/problems/1380731/ RHBZ#995785 http://retrace.fedoraproject.org/faf/problems/1380807/ RHBZ#995785
2. gnome-software seen 5545 times (10% of all reports) http://retrace.fedoraproject.org/faf/problems/1343678/ RHBZ#1013270 http://retrace.fedoraproject.org/faf/problems/1403433/ RHBZ#1044237
3. kernel seen 4540 times (8% of all reports) http://retrace.fedoraproject.org/faf/problems/898437/ http://retrace.fedoraproject.org/faf/problems/1372844/
4. rhythmbox seen 2593 times (5% of all reports) http://retrace.fedoraproject.org/faf/problems/1452772/ RHBZ#1047018 http://retrace.fedoraproject.org/faf/problems/1241887/ RHBZ#1013858
5. tracker seen 2273 times (4% of all reports) http://retrace.fedoraproject.org/faf/problems/1206163/ RHBZ#957533 http://retrace.fedoraproject.org/faf/problems/1374021/ RHBZ#1031752
Hot problems:
ID Components Count ------------------------------------------------------- 1380731 gnome-shell 7408 1452772 rhythmbox 2030 1343678 gnome-software 1413 1160652 speech-dispatcher 976 1261972 open-vm-tools 840 1355243 kernel 557 1380807 gnome-shell 529 1324026 gnome-tweak-tool 467 1287308 gnome-shell 458 1282601 nautilus 434
URL: http://retrace.fedoraproject.org/faf/problems/hot/fedora-20/*/*/
Long-term problems:
ID Components Count ------------------------------------------------------- 1380731 gnome-shell 8074 1127716 glib-networking 5946 1160652 speech-dispatcher 2451 1343678 gnome-software 2185 1261972 open-vm-tools 1942 1250468 gnome-tweak-tool 1484 1324026 gnome-tweak-tool 1283 1282601 nautilus 1125 1178557 kernel 891 250996 udisks2 674
URL: http://retrace.fedoraproject.org/faf/problems/longterm/fedora-20/*/*/
Server URL: http://retrace.fedoraproject.org/faf/ Report a bug: https://github.com/abrt/faf/issues/new Server sources: https://github.com/abrt/faf
On Fri, Jan 3, 2014 at 9:29 AM, Richard Marko rmarko@redhat.com wrote:
In last two weeks these components were crashing the most on Fedora 20: 3. kernel seen 4540 times (8% of all reports) http://retrace.fedoraproject.org/faf/problems/898437/ http://retrace.fedoraproject.org/faf/problems/1372844/
Is there some way to flag package versions as obsolete in retrace? The first report above is for a 3.9 kernel that we don't even support any more because F18 is well past 3.9.
The second report is for a problem in a proprietary wireless driver that we don't ship or support. We've asked before, but apparently there's no way to stop from including that kind of thing in retrace?
I think retrace has a great opportunity to really help with data gathering, but if we can't filter that data into something people can actually use I'm worried it will just sit by the wayside.
josh
On 01/03/2014 03:35 PM, Josh Boyer wrote:
On Fri, Jan 3, 2014 at 9:29 AM, Richard Marko rmarko@redhat.com wrote:
In last two weeks these components were crashing the most on Fedora 20: 3. kernel seen 4540 times (8% of all reports) http://retrace.fedoraproject.org/faf/problems/898437/ http://retrace.fedoraproject.org/faf/problems/1372844/
Is there some way to flag package versions as obsolete in retrace? The first report above is for a 3.9 kernel that we don't even support any more because F18 is well past 3.9.
Currently no. It should be possible to integrate faf with bodhi so the server would be aware of obsolete packages.
The second report is for a problem in a proprietary wireless driver that we don't ship or support. We've asked before, but apparently there's no way to stop from including that kind of thing in retrace?
We want tainted reports but we won't show them or include them in these statistics by default.
Related issues https://github.com/abrt/faf/issues/189 https://github.com/abrt/faf/issues/219