Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 662472 Details for
Bug 886607
[abrt] gvfs-obexftp-1.12.3-1.fc17: g_thread_abort: Process /usr/libexec/gvfsd-obexftp was killed by signal 6 (SIGABRT)
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
File: event_log
event_log (text/plain), 3.63 KB, created by
ali
on 2012-12-12 16:38:24 UTC
(
hide
)
Description:
File: event_log
Filename:
MIME Type:
Creator:
ali
Created:
2012-12-12 16:38:24 UTC
Size:
3.63 KB
patch
obsolete
>2012-12-12-19:28:01> Could not resolve host: retrace.fedoraproject.org; Unknown error >2012-12-12-19:28:01* (exited with 1) >2012-12-12-19:29:26> (exited with 0) >2012-12-12-19:29:31> Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' >2012-12-12-19:29:31 Querying server settings >2012-12-12-19:29:50 Preparing an archive to upload >2012-12-12-19:29:55 Uploading 120188 bytes >2012-12-12-19:30:05 Upload successful >2012-12-12-19:30:08 An error occurred on the server side. Try again later. >2012-12-12-19:30:08 Unable to obtain unpacked size >2012-12-12-19:30:10 Do you want to generate a stack trace localy? (It may download a huge amount of data but reporting can't continue without stack trace). 'YES' >2012-12-12-19:30:11 Analyzing coredump 'coredump' >2012-12-12-19:30:12 Coredump references 27 debuginfo files, 27 of them are not installed >2012-12-12-19:30:13 Setting up yum repositories >2012-12-12-19:30:17* (killed by signal 15) >2012-12-12-19:59:11> (exited with 0) >2012-12-12-19:59:13> Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' >2012-12-12-19:59:14 Querying server settings >2012-12-12-19:59:17 Preparing an archive to upload >2012-12-12-19:59:19 Uploading 120188 bytes >2012-12-12-19:59:20 Upload successful >2012-12-12-19:59:23 Retrace job started >2012-12-12-19:59:35 Preparing environment for backtrace generation >2012-12-12-19:59:49 Preparing environment for backtrace generation >2012-12-12-20:00:04 Preparing environment for backtrace generation >2012-12-12-20:00:18 Preparing environment for backtrace generation >2012-12-12-20:00:34 Preparing environment for backtrace generation >2012-12-12-20:00:47 Preparing environment for backtrace generation >2012-12-12-20:00:59 Preparing environment for backtrace generation >2012-12-12-20:01:11 Preparing environment for backtrace generation >2012-12-12-20:01:30 Preparing environment for backtrace generation >2012-12-12-20:01:45 Preparing environment for backtrace generation >2012-12-12-20:01:57 Preparing environment for backtrace generation >2012-12-12-20:02:12 Preparing environment for backtrace generation >2012-12-12-20:02:23 Preparing environment for backtrace generation >2012-12-12-20:02:38 Preparing environment for backtrace generation >2012-12-12-20:02:51 Preparing environment for backtrace generation >2012-12-12-20:03:06 Preparing environment for backtrace generation >2012-12-12-20:03:20 Preparing environment for backtrace generation >2012-12-12-20:03:35 Preparing environment for backtrace generation >2012-12-12-20:03:50 Preparing environment for backtrace generation >2012-12-12-20:04:04 Preparing environment for backtrace generation >2012-12-12-20:04:19 Preparing environment for backtrace generation >2012-12-12-20:04:33 Preparing environment for backtrace generation >2012-12-12-20:04:48 Preparing environment for backtrace generation >2012-12-12-20:05:02 Preparing environment for backtrace generation >2012-12-12-20:05:16 Preparing environment for backtrace generation >2012-12-12-20:05:30 Preparing environment for backtrace generation >2012-12-12-20:05:45 Preparing environment for backtrace generation >2012-12-12-20:05:58 Preparing environment for backtrace generation >2012-12-12-20:06:13 Preparing environment for backtrace generation >2012-12-12-20:06:27 Preparing environment for backtrace generation >2012-12-12-20:06:42 Cleaning environment after backtrace generation >2012-12-12-20:06:56 Retrace job finished successfully >2012-12-12-20:07:15> Smolt profile successfully saved
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 886607
:
662469
|
662470
|
662471
| 662472 |
662473
|
662474
|
662475
|
662476
|
662477
|
662478
|
662479
|
662480
|
662481
|
662482