Description of problem: I have enabled snapperd as a yum plugin. Everytime there's an update, it's launched a go through the snapshost to compute differences (to allow you to rollback files and so on), that's when it crashes. Version-Release number of selected component: snapper-0.1.7-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: snapperd crash_function: exit executable: /usr/sbin/snapperd kernel: 3.13.0 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (2 frames) #19 exit at exit.c:104 #21 _start
Created attachment 855489 [details] File: backtrace
Created attachment 855490 [details] File: cgroup
Created attachment 855491 [details] File: core_backtrace
Created attachment 855492 [details] File: dso_list
Created attachment 855493 [details] File: limits
Created attachment 855494 [details] File: maps
Created attachment 855495 [details] File: open_fds
Created attachment 855496 [details] File: proc_pid_status
Another user experienced a similar problem: I did a root: snapper create --command "yum install epiphany" --description "epiphany" to create a pre and post snapshot for running "yum install epiphany". 5 minutes after snapper crashed. However, I did a few snapper create --command "yum install softwarehere" --description "description here" and it did not crash after while. Do note however that the snapshots are working. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/sbin/snapperd crash_function: exit executable: /usr/sbin/snapperd kernel: 3.14.9-200.fc20.x86_64 package: snapper-0.1.7-1.fc20 reason: snapperd killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.