Hello, thank you for taking the time to report this issue. ABRT server rejected the stack trace because some frames did not have function name. We are not sure what causes it but it is probably related to a memory issue.

abrt-2.2.2 [1] and satyr-0.14 [2] attempt to fix this problem. Please update abrt, libreport and satyr packages, wait for a new crash, report it and report the results here.

1: https://admin.fedoraproject.org/updates/abrt-2.2.2-1.fc20,libreport-2.2.3-1.fc20
2: https://admin.fedoraproject.org/updates/FEDORA-2014-7258/satyr-0.14-1.fc20

(In reply to Jakub Filak from comment #1)
> Hello, thank you for taking the time to report this issue. ABRT server
> rejected the stack trace because some frames did not have function name. We
> are not sure what causes it but it is probably related to a memory issue.
> 
> abrt-2.2.2 [1] and satyr-0.14 [2] attempt to fix this problem. Please update
> abrt, libreport and satyr packages, wait for a new crash, report it and
> report the results here.
> 
> 1:
> https://admin.fedoraproject.org/updates/abrt-2.2.2-1.fc20,libreport-2.2.3-1.
> fc20
> 2: https://admin.fedoraproject.org/updates/FEDORA-2014-7258/satyr-0.14-1.fc20

Ok, I'll do it.

Thanks.

I have updated and now all seems working.
Turpial crashed and I was able to submit a report trought abrt.

Thanks.

Hi,

I seem to be getting the same issue on F21 but I already have the updated packages:

[asinha@localhost  ~]$ rpm -q abrt
abrt-2.2.2-4.fc21.x86_64
[asinha@localhost  ~]$ rpm -q libreport
libreport-2.2.3-4.fc21.x86_64
[asinha@localhost  ~]$ rpm -q satyr
satyr-0.14-3.fc21.x86_64

I've only seen this occur when gnome-shell crashes, though. I get this:

--- Running report_uReport ---
Server responded with an error: 'Validation failed: Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing'
reporter-ureport failed with exit code 1
('report_uReport' exited with 1)

Thanks,
Warm regards,
Ankur

I got similar errors this summer on my Fedora 20 system multiple times. Didn't file a bug report, but I'll give the info here if I get them again.

Was very similar to this "'--- Running report_uReport ---
Server responded with an error: 'Validation failed: Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing'
reporter-ureport failed with exit code 1
('report_uReport' exited with 1)'", I couldn't file bugs.

Hello, Michal Toman has been working hard over the last days and this issue should be fixed now. Could you please try again to report your gnome-shell crashes?

(In reply to Jakub Filak from comment #6)
> Hello, Michal Toman has been working hard over the last days and this issue
> should be fixed now. Could you please try again to report your gnome-shell
> crashes?

Hi Jakub

I haven't had any gnome-shell crashes that didn't go through yet. I'll post again if I do.

Thanks for working on this. 
Regards,
Ankur

I had this when I was logged into the root account today, there was an bug and I couldn't report it because of the same looking error, can't remember if it was the same exactly.

But it was in Fedora 20 KDE x86_64

(In reply to Kristjan Stefansson from comment #9)
> But it was in Fedora 20 KDE x86_64

Could you please attach the dump directory (it is an one of /var/tmp/abrt/ccpp*)? We haven't seen this error for KDE binaries yet.

I looked in /var/tmp/abrt/ccpp* but it only had two crashes(kills) and looked at the "reason", I couldn't see any connection to those to "abrt", I also logged back into root and tried to report the two but it was successful(bugs already reported) so I am unable to repreduce the error.

But if you think there are any traces on these errors on my system let me know, I've been using KDE all this time, so the errors I mentioned somewere about this problem where all on KDE, both my user account and root(in the last two days).

I got something similar today over a py crash. I'm not sure if it's related:

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Running report_Bugzilla ---
Essential element 'global_uuid' is missing, can't continue
('report_Bugzilla' exited with 1)

--- Running report_Bugzilla ---
Essential element 'global_uuid' is missing, can't continue
('report_Bugzilla' exited with 1)

It was a crash in the hamster-time-tracker package.

(In reply to Ankur Sinha (FranciscoD) from comment #13)
Thanks, but this is something completely different. Could you please open a new bug and attach the related dump directory (/var/tmp/abrt/*).

I see this when trying to report a guayadeque crash on FC21


--- Running report_uReport ---
Server responded with an error: 'Validation failed: Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing'
reporter-ureport failed with exit code 1
('report_uReport' exited with 1)

Created attachment 946284 [details]
ccpp directory

(In reply to Mark van Rossum from comment #15)
The error message server returns is awful and has poor information value for regular users. The problem in your case is that 'coredump' is damaged and 'stacktrace' is invalid. We have already made the code more permissive and now, we must wait until the updates land in production.

core_backtrace:
...
{   "crash_thread": true
        ,   "frames":
              [ {   "address": 0
                ,   "build_id_offset": 0
                } ]
        }
...

I believe this bus is fixed now. Please feel free to re-open if needed.

Its rearing its UGLY head again. The MONSTER wont DIE.

--- Running report_uReport ---
Server responded with an error: 'uReport data is invalid.'
reporter-ureport failed with exit code 1
('report_uReport' exited with 1)