Bug 690890 - [abrt] deja-dup-15.3-2.fc14: Process /usr/bin/deja-dup was killed by signal 11 (SIGSEGV)
Summary: [abrt] deja-dup-15.3-2.fc14: Process /usr/bin/deja-dup was killed by signal 1...
Keywords:
Status: CLOSED DUPLICATE of bug 699258
Alias: None
Product: Fedora
Classification: Fedora
Component: deja-dup
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:af65c55f29815f0c54bedce55a2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-25 17:22 UTC by LR
Modified: 2012-03-21 16:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 16:25:44 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (23.82 KB, text/plain)
2011-03-25 17:22 UTC, LR 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description LR 2011-03-25 17:22:42 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 24395 bytes
cmdline: deja-dup --restore x-nautilus-desktop:///computer
component: deja-dup
Attached file: coredump, 38051840 bytes
crash_function: g_file_make_directory_with_parents
executable: /usr/bin/deja-dup
kernel: 2.6.35.6-45.fc14.i686
package: deja-dup-15.3-2.fc14
rating: 4
reason: Process /usr/bin/deja-dup was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301057225
uid: 500

comment
-----
First time Installation from Livecd. Running long update and system froze. Forced to continue by Yum update command in terminal.
Experienced several crashes into black screen. Rebooting by powering off.

How to reproduce
-----
1.Ran ordinary update 
2.OS abruptly crashed and went into black screen
3.
Comment 1 LR 2011-03-25 17:22:45 UTC 
Created attachment 487625 [details]
File: backtrace
Comment 2 Michael Terry 2011-04-04 01:39:55 UTC 
This is fixed in trunk, will be in 18.0.
Comment 3 abrt-bot 2012-03-21 16:25:44 UTC 
Backtrace analysis found this bug to be similar to bug #699258, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 699258 ***
Note You need to log in before you can comment on or make changes to this bug.