Bug 541734 - Back In Time crash after completion of backup
Summary: Back In Time crash after completion of backup
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: backintime
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-26 21:25 UTC by Mark Walker
Modified: 2010-05-27 19:17 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-27 19:17:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
backtrace (161.39 KB, text/plain)
2009-11-26 21:25 UTC, Mark Walker
no flags Details
backtrace (35.33 KB, text/plain)
2009-11-26 21:47 UTC, Christoph Wickert
no flags Details

Description Mark Walker 2009-11-26 21:25:53 UTC
Created attachment 374069 [details]
backtrace

Description of problem:
Crash after completion of backup.

Version-Release number of selected component (if applicable):
Back In Time
Version 0.9.26
Using KDE 4.3.3 (KDE 4.3.3)

How reproducible:
Run Snapshot process in Back in Time utility

Steps to Reproduce:
1. Set cron job to run hourly backup and set source folders and backup share.

2. Cron job line is as follows:
@hourly nice -n 19 /usr/bin/backintime --backup-job >/dev/null 2>&1

3.Allow cron to run.
  
Actual results:
Backup runs; then crash after backup is finished.

Expected results:
Completed backup with no errors.  This happens about half the time.

Additional info:
See attached file:///var/log/abrt-logger
UUID: dd9b966282920846594fda2b3bc8b9459236cf12
architecture: x86_64
cmdline: python /usr/share/backintime/common/backintime.py --backup-job
component: python

Comment 1 Christoph Wickert 2009-11-26 21:46:09 UTC
Comment on attachment 374069 [details]
backtrace

I guess one backtrace is enough.

Comment 2 Christoph Wickert 2009-11-26 21:47:25 UTC
Created attachment 374073 [details]
backtrace

Comment 3 Tim Jackson 2010-05-27 19:17:55 UTC
Reported upstream as https://bugs.launchpad.net/fedora/+source/backintime/+bug/586501


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