Bug 1010222

Summary: [abrt] deja-dup-26.0-1.fc19: gtk_tree_model_get_valist: Process /usr/bin/deja-dup was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Vladimir Krcho <vlkovo>
Component: deja-dupAssignee: Rahul Sundaram <metherid>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: fedora, jitesh.1337, kengert, lonelywoolf, metherid, mike
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:9bc82e5867b7854ee61c047ec079054def86811e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-18 11:18:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Vladimir Krcho 2013-09-20 10:01:01 UTC
Description of problem:
After running recovery 
...
Where to recover
- Recover to specified directory 
- select other... & crash

Version-Release number of selected component:
deja-dup-26.0-1.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        deja-dup --restore
crash_function: gtk_tree_model_get_valist
executable:     /usr/bin/deja-dup
kernel:         3.11.1-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gtk_tree_model_get_valist at gtktreemodel.c:1765
 #1 gtk_tree_model_get at gtktreemodel.c:1727
 #2 combo_box_row_separator_func at gtkfilechooserbutton.c:2388
 #3 tree_column_row_is_sensitive at gtkcombobox.c:2188
 #4 gtk_combo_box_list_button_released at gtkcombobox.c:3752
 #5 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
 #10 gtk_widget_event_internal at gtkwidget.c:6714
 #11 gtk_widget_event at gtkwidget.c:6371
 #12 propagate_event_up at gtkmain.c:2393
 #13 propagate_event at gtkmain.c:2501

Comment 1 Vladimir Krcho 2013-09-20 10:01:07 UTC
Created attachment 800383 [details]
File: backtrace

Comment 2 Vladimir Krcho 2013-09-20 10:01:10 UTC
Created attachment 800384 [details]
File: cgroup

Comment 3 Vladimir Krcho 2013-09-20 10:01:14 UTC
Created attachment 800385 [details]
File: core_backtrace

Comment 4 Vladimir Krcho 2013-09-20 10:01:19 UTC
Created attachment 800386 [details]
File: dso_list

Comment 5 Vladimir Krcho 2013-09-20 10:01:23 UTC
Created attachment 800387 [details]
File: environ

Comment 6 Vladimir Krcho 2013-09-20 10:01:27 UTC
Created attachment 800388 [details]
File: exploitable

Comment 7 Vladimir Krcho 2013-09-20 10:01:30 UTC
Created attachment 800389 [details]
File: limits

Comment 8 Vladimir Krcho 2013-09-20 10:01:35 UTC
Created attachment 800390 [details]
File: maps

Comment 9 Vladimir Krcho 2013-09-20 10:01:39 UTC
Created attachment 800391 [details]
File: open_fds

Comment 10 Vladimir Krcho 2013-09-20 10:01:42 UTC
Created attachment 800392 [details]
File: proc_pid_status

Comment 11 Vladimir Krcho 2013-09-20 10:01:46 UTC
Created attachment 800393 [details]
File: var_log_messages

Comment 12 lonelywoolf 2013-09-30 07:05:12 UTC
I have the same error. Have anybody workaround? Sorry for my bad english.

Comment 14 Fedora End Of Life 2015-01-09 22:40:10 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2015-02-18 11:18:44 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.