Bug 903182 - nepomukservicestub was killed by signal 11, ABRT fails to upload bug report
Summary: nepomukservicestub was killed by signal 11, ABRT fails to upload bug report
Keywords:
Status: CLOSED DUPLICATE of bug 904183
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-23 12:14 UTC by Michael
Modified: 2016-12-01 00:43 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-31 09:05:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
abrt-data.tar.gz last crash dumps (32.88 MB, application/octet-stream)
2013-01-24 10:38 UTC, Michael
no flags Details

Description Michael 2013-01-23 12:14:51 UTC
Description of problem:

Every Time i (re) start my fc18/KDE nepomukservice(tub) ABRT came up. But i can not report a Bug. Msg is:

--- Running report_uReport ---
Server-seitiger Fehler: »"Validation failed: error validating 'core_backtrace': error validating 'funchash': string \"\/usr\/bin\/nepomukservicestub\" contains illegal characters"«
(exited with 1)

Version-Release number of selected component (if applicable):

4.9.5-1.fc18 (x86_64)

How reproducible:

(re) start fc18/KDE

Steps to Reproduce:
1. shutdown fc18/KDE
2. (re)boot fc18/KDE
3. nepomuk crashes and can not send bugreport: because 'core_backtrace' have : "contains illegal characters"
  
Actual results:


Expected results:


Additional info:

Comment 1 Kevin Kofler 2013-01-24 00:29:01 UTC
There's an ABRT bug there. Unfortunately, with the little information we have as a result, it's impossible to do anything about the nepomukservicestub bug. I'm reassigning the bug to ABRT in the hope that they'll fix the issue on their end so we get some actual data from ABRT.

Comment 2 Kevin Kofler 2013-01-24 00:30:16 UTC
(note: "Server-seitiger Fehler" means "server-side error.")

Comment 3 Jakub Filak 2013-01-24 08:39:00 UTC
Please attach the dump directory for analysis (it should be located either in ~/.cache/abrt/spool/ or in /var/spool/abrt/).

Comment 4 Michael 2013-01-24 10:26:00 UTC
thanks for fast answer! 

@kevin: thanks (dankeschön!) for translation

i found dump(s) in both folders

@~/.cache/abrt/spool/ i found a folder /abrt
@/var/spool/abrt/ i found my last crash (sorry, its a wireshark app crash) but this report I could not

Attachment: abrt-data.tar.gz

Comment 5 Michael 2013-01-24 10:38:31 UTC
Created attachment 686647 [details]
abrt-data.tar.gz last crash dumps

Comment 6 Jakub Filak 2013-01-31 09:05:19 UTC
Thank you for the bug report. We really appreciate your help. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 904183 ***


Note You need to log in before you can comment on or make changes to this bug.