+++ This bug was initially created as a clone of Bug #1374648 +++

Description of problem:
abrt-cli report fails to report vmcore problem directories. The cause appears to be since backtrace file is empty.

How reproducible:
Always

Steps to Reproduce:
# abrt-cli report /var/spool/abrt/vmcore-127.0.0.1-2016-09-08-01:05:49
Can't find a meaningful backtrace for hashing in '.'
('analyze_VMcore' exited with 1)

# abrt-cli report /var/spool/abrt/vmcore-127.0.0.1-2016-09-08-01\:05\:49
Can't find a meaningful backtrace for hashing in '.'
('analyze_VMcore' exited with 1)

# abrt-cli report /var/spool/abrt/vmcore-127.0.0.1-2016-09-08-01\:05\:49/
Can't chown '/var/spool/abrt/vmcore-127.0.0.1-2016-09-08-01:05:49/': GDBus.Error:org.freedesktop.problems.InvalidProblemDir: '/var/spool/abrt/vmcore-127.0.0.1-2016-09-08-01:05:49/' is not a valid problem directory
Can't take ownership of '/var/spool/abrt/vmcore-127.0.0.1-2016-09-08-01:05:49/'

Actual results:
# abrt-cli report /var/spool/abrt/vmcore-127.0.0.1-2016-09-08-01:05:49

The vmcore-127.0.0.1-2016-09-08-01.tar.gz file is uploaded at
http://10.65.5.157/files/vmcore-127.0.0.1-2016-09-08-01.tar.gz

Expected results:
Successfull abrt reporting.

NOTE: Above is part of original description of RHEL bug. In fact this exact vmcore problem can't be fully reportable to Fedora, because it appeared on RHEL. This bug is considered fixed and tested for Fedora, when abrt-dump-oops tool produces meaningful Backtrace file for linked problem directory. This fix will cause working of whole reporting process on RHEL if another problem wouldn't appear.