Version-Release number of selected component: deja-dup-37.1-1.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=30b14ed7b3c04505ab18609998a4224a;i=3c596;b=f2123d5ad7d34ddf8d53a842e6f640a2;m=22bf23c;t=5676e841054ed;x=50bf8599080e3f97 kernel: 4.15.9-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 Gigacage::<lambda()>::operator() at /usr/src/debug/webkitgtk4-2.20.0-1.fc27.x86_64/Source/bmalloc/bmalloc/Gigacage.cpp:154 #1 std::__invoke_impl<void, Gigacage::ensureGigacage()::<lambda()> > at /usr/include/c++/7/bits/invoke.h:60 #2 std::__invoke<Gigacage::ensureGigacage()::<lambda()> > at /usr/include/c++/7/bits/invoke.h:95 #3 std::<lambda()>::operator() at /usr/include/c++/7/mutex:672 #5 std::<lambda()>::_FUN(void) at /usr/include/c++/7/mutex:677 #6 __pthread_once_slow at pthread_once.c:116 #7 __gthread_once at /usr/include/c++/7/x86_64-redhat-linux/bits/gthr-default.h:699 #8 std::call_once<Gigacage::ensureGigacage()::<lambda()> > at /usr/include/c++/7/mutex:684 #9 Gigacage::ensureGigacage at /usr/src/debug/webkitgtk4-2.20.0-1.fc27.x86_64/Source/bmalloc/bmalloc/Gigacage.cpp:108 #10 bmalloc::Heap::Heap at /usr/src/debug/webkitgtk4-2.20.0-1.fc27.x86_64/Source/bmalloc/bmalloc/Heap.cpp:58 Potential duplicate: bug 1527888
Created attachment 1408345 [details] File: backtrace
Created attachment 1408346 [details] File: cgroup
Created attachment 1408347 [details] File: core_backtrace
Created attachment 1408348 [details] File: cpuinfo
Created attachment 1408349 [details] File: dso_list
Created attachment 1408350 [details] File: environ
Created attachment 1408351 [details] File: exploitable
Created attachment 1408352 [details] File: limits
Created attachment 1408353 [details] File: maps
Created attachment 1408354 [details] File: mountinfo
Created attachment 1408355 [details] File: open_fds
Created attachment 1408356 [details] File: proc_pid_status
Same here. What is going on with that very important utility ? It seems that automatic scheduled backup broken for me more then year ( only manual backup work).
Similar problem has been detected: After login, soon reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=0bf381d7d40b4433818fc87fb1d40bac;i=335c09;b=28dda9196fa343ed81bdb3e58c41c678;m=1520646e;t=56791fd050d13;x=f24eab7083ddb9c kernel: 4.15.9-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: computer booting and notation about crash and can't continue reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=abda5f6e7ad24c10a2cebfb60882c130;i=905;b=0d4f5d6e8ce641fa898bbf34c82262cd;m=1abcf09;t=5677114d1a0ef;x=9de79e33b6b198fa kernel: 4.15.8-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Random crash, cannot reproduce reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=ed8b4215c2144aee822960b01087fbf7;i=53697b;b=d6dde59963494a5a87c97288d521d756;m=1c3d8d5;t=567c1a9e70837;x=5b9d2a5170524e5d kernel: 4.15.10-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Start up the system, during login, this is produced reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=6b165992a35c4e75b35edb3fe7c8fda1;i=ad46;b=abbe0f60d8ab4e0cafb7b0ae1af20dad;m=276d260;t=5675b6c0eefb2;x=b153115f8ae4f9f1 kernel: 4.15.9-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1527888 has been marked as a duplicate of this bug. ***
See https://bugs.webkit.org/show_bug.cgi?id=183329#c22 or https://bugs.launchpad.net/deja-dup/+bug/1751460 for explanation: """ webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an extremely large virtual memory address space (much larger than available physical memory). Deja Dup's monitor background service had "ulimit -v 1000000" (that's 1 GB) set as a workaround for a memory leak issue that the developer was unable to reproduce. After upgrading to the new webkit2gtk version, Deja Dup's monitor service will crash because of that virtual memory limit. """ Deja Dup needs to remove the ulimit it sets in its desktop file, which prevents WebKit from allocating the huge address space it needs for the Gigacage.
Similar problem has been detected: Reproduce: 1. Open deja-dup 2. Select (unscheduled) 'Back Up Now...' button Note: deja-dup missed prior weekly prompt to backup. Application failed to prompt for password and connect to netowrk device reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=7726eb56b38c46889bb06923fe315905;i=1108f;b=415f50ec13d847c4b4d31aea2286a3b5;m=6920706;t=56829414a00e5;x=77877453c163c878 kernel: 4.15.12-301.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: The crash notification appears right after logging into Gnome Shell. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=c915b4b30af843fa81060d930eb509d9;i=f0dc8;b=a81b72d100284a99aa025a8500560c46;m=71b417;t=5675c3c662288;x=e178a39b5aa354b0 kernel: 4.15.9-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 501
Similar problem has been detected: On login the backup-monitor daemon fails to start reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=805b1904aa06454881216cd7f76ccd17;i=fb8;b=e41bd55230774bbabf96d2bfc1b2b76a;m=98757d7;t=5681dde47555c;x=5a83ac30a9d7ff44 kernel: 4.15.11-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: crash occured with login reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=73ec18e8c3384ad78db9a40c62fe8735;i=523944;b=164e005a231340cab371fa1cedc22a4f;m=19d12de;t=5693558cc0fb5;x=3460d3df8d165f8f kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Deja dup had a window open (Ithink about that the (external) backup location could not be found). I inserted my phone as USB storage device. The crash happened directly after inserting the phone as USB storage device. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: deja-dup --backup --auto crash_function: Gigacage::<lambda()>::operator() executable: /usr/bin/deja-dup journald_cursor: s=514aa427b650453d977961ada3a4e20d;i=7336;b=aa7f337f21e24c77871227fa71d2aeaf;m=117e72dea6;t=5693f6640f8de;x=e40b94864c9f2924 kernel: 4.15.13-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: This happened when connecting the external usb disk that I use as the backup target device. I guess the crash is somehow related to mounting (usb) disks. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: deja-dup --backup --auto crash_function: Gigacage::<lambda()>::operator() executable: /usr/bin/deja-dup journald_cursor: s=514aa427b650453d977961ada3a4e20d;i=774d;b=aa7f337f21e24c77871227fa71d2aeaf;m=134461c263;t=569412c2fdc9c;x=3459846915fa9b48 kernel: 4.15.13-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1564816 has been marked as a duplicate of this bug. ***
*** Bug 1564842 has been marked as a duplicate of this bug. ***
Similar problem has been detected: On startup and login to account after dnf update of system on 4/7/2018 reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=5e049b81393740ee88e4a22470cc27cf;i=8ba;b=183d7598defe41ef98dfee790a3d5748;m=2281f19;t=5694f215b5b1e;x=7609570f8d0109f kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: 1 5 type: CCpp uid: 1000
*** Bug 1564886 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Crash after reboot / login reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=bf2017014bbd42d3a360135cf4c6c7ad;i=56ed0f;b=927696d535ed475a846c69ffa8d1d0fd;m=97f1c723;t=56958b13b0eed;x=d8c0d5a577d44834 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Got the error right after booting in Gnome. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=b5b80904057748caad2843712603f192;i=110cb;b=6c43e074d5dd4c549b59fc49118688f7;m=1ee6081;t=5693f7fd540b0;x=efdf3e1c5b475204 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: just booting / loggin in. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=699b7a69b4db4c33ab8b4d70665d7c2e;i=6b13;b=33880704b5d546cbb98db4cd52cd2362;m=329c159;t=5695b7b9ab650;x=9124e321641aeff4 kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happened following system boot up. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=3095a9c1c2684aaebb2434f4702a2706;i=74c56;b=e6a28e5a1a5c4e4ebd55c53e55bb8085;m=63b1ebe;t=5695c8c841628;x=9ab433ebc886ee6e kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: failed at startup reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=c7c05341a9f4474080e48413d4945ef9;i=be81;b=5991c2981b1140a4ad39913d6d7fd67b;m=2ca8e2aa;t=569499a0a7cff;x=3a8dded09b3496d5 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: login to gnome-shell reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=a06bab7203c641ba95c4356e697fb40b;i=946352;b=21eaa7e8519d41ffbdf80e8551769d29;m=353b047;t=56955e06dcedd;x=58fb35d45179e782 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1106
Similar problem has been detected: The crash appeared right after a fresh restart. The machine had been off for the night and when restarting I got the crash. I do not know what the cause was. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=538a2682203c4437af8f933df1d5b262;i=3e1b;b=be7bcbd5556d4e8eb52b965bef4a105e;m=1610ce1;t=569640a7a22f6;x=1334624f8afa44f6 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Booted up my laptop, logged into Cinnamon session. Applied 44 updates via dnfdragora then rebooted. Logged into Cinnamon session and almost immediately got the error report. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=4c69f9b65046467d8b4a8f0f1926ecd7;i=1f18d4;b=01854f0f8cf04d29ae19214380a40487;m=953f327;t=56969a13d5f54;x=7e0b655abb44cb95 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: This happens during login reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=cb975d7eacbb489d84866d9588a6796f;i=3f085;b=ecb1846ea5d745cd9aa35e373714de91;m=1ed86e4;t=5695c6d20c55f;x=e2c431723531925a kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Immediately reported on start-up reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=0dd91224dd034fb2a5274ae9238a0079;i=b1a6c;b=2f76a293c081455b95472f287398e506;m=ea3fd64;t=569501c8c63df;x=2f7336a107e8d797 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
A fix (removing the ulimit) has been merged in master in Fedora: https://src.fedoraproject.org/rpms/deja-dup/pull-request/2 Expecting builds and updates to follow.
Similar problem has been detected: Crashes during the login process with no user interaction reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=b436104748f34a1c81420e13fdbf413b;i=17bfa0;b=30da16aa66ef4ee4902a80dde22caa1a;m=1564fe6;t=569531830a7d5;x=4338cc5d7f8c5813 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 501
Similar problem has been detected: Crash after start computer reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=63045d2b79604f998553c0b04eb55ad5;i=1b940;b=d89d2e62e907484cadadc77e28364760;m=670b0a2e;t=56968fa8cb48f;x=ab6c9683d59cbb7f kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
deja-dup-37.1-4.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b2f39cabc4
deja-dup-37.1-4.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-6f518ef785
deja-dup-37.1-4.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-35b38273b9
*** Bug 1565771 has been marked as a duplicate of this bug. ***
deja-dup-37.1-4.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-35b38273b9
deja-dup-37.1-4.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b2f39cabc4
deja-dup-37.1-4.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-6f518ef785
Similar problem has been detected: error has been occuring right after powering computer on and as soon as it boots to desktop reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=5d4783732251487d96f8d60e5e62f084;i=c4770;b=ba3aa4d3907246388f9c43951ef68c8d;m=43df5a8;t=5695b911dd80d;x=b2621dc34f8e435c kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
looks like deja-dup-37.1-4.fc28 from updates-testing solved it, tanks
Similar problem has been detected: At system starup happend after I logged in. Backup target is in the network by ssh. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=69aa5dc0453d4b018a962cd6889e9687;i=1650b8;b=a1a1104b28b24324b6771b1dd356125b;m=bdd13df;t=5693bcf4c3f4c;x=76b8f809605c2f07 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
(In reply to Szőke Károly from comment #52) > Similar problem has been detected: > > At system starup happend after I logged in. Backup target is in the network > by ssh. > > reporter: libreport-2.9.3 > backtrace_rating: 4 > cmdline: /usr/libexec/deja-dup/deja-dup-monitor > crash_function: Gigacage::<lambda()>::operator() > executable: /usr/libexec/deja-dup/deja-dup-monitor > journald_cursor: > s=69aa5dc0453d4b018a962cd6889e9687;i=1650b8; > b=a1a1104b28b24324b6771b1dd356125b;m=bdd13df;t=5693bcf4c3f4c; > x=76b8f809605c2f07 > kernel: 4.15.14-300.fc27.x86_64 > package: deja-dup-37.1-1.fc27 > reason: deja-dup-monitor killed by SIGSEGV > rootdir: / > runlevel: N 5 > type: CCpp > uid: 1000 I installed the update, it seems to works. Thx.
I installed the update on Tuesday. It made the startup problem go away. This morning was my scheduled update and it did so without issue. The repair seems to have nailed it.
Similar problem has been detected: Happens during logging into gnome desktop, on both Wayland & Xorg. Enter password and a few seconds after desktop is created the oops message appears reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=597b8ec3e33942338c319ff863324367;i=2066ea;b=50648eb6e9ae4e1c9bde51a1e9f51590;m=2445e10;t=569a6157c5503;x=2d48644d0abc6861 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: This happened during reboot. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=1e400ac614194c65b88106f5e856084c;i=60d10;b=6f219013c6ea4c8abeaba591112e5221;m=bab96e3;t=5697db20f0137;x=a066b8344f87c8fe kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happens everytime I boot the computer reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=89525de521f540eb8d74b90125a9af3c;i=10919;b=b31c4631643b49afb2512bfab6108db1;m=fa4831;t=56984733c39d9;x=2381eaecd805223e kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: unknown type: CCpp uid: 1000
Similar problem has been detected: Start Gnome after an init 6 to perform a reboot; deja crashed on restart after going back to Gnome3 reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=b6da05ea7e4a4b9187fb1e9933fc6d43;i=30874b;b=1e15da971b84466d9ca7239f505acd55;m=1c4ba94;t=569a931ebb126;x=607491446277d3ff kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: unknown type: CCpp uid: 1000
*** Bug 1566653 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This happens soon after login on a freshly booted system. I was not using the deja-dup gui at the time of the crash, it happened spontaneously. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=3e85e4456e8d4385958fa7015f1b36fd;i=b2ba3;b=fb983b62a7bf4a81b3960676f8999b04;m=187dce3d;t=56973356595ee;x=41aad9a4ccaa4fd5 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Logged in reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=65bca0d929574dcd9a32c08afa671f78;i=1b891;b=049f4556e8894fcdac6eba396c714c62;m=4749592;t=569b02e5b79a4;x=7d9d9f3af8656bd kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Happens everytime I login into GNOME lately. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=2a0d22bdd473495082a6148d04d5aa75;i=6c3a;b=511cbccfa8b942738434f8d34e1b7ddf;m=2f36aca;t=569a05b5bfff8;x=df9eaffb075e8b60 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Problem reported in the notification window on system startup. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=0d3ac7b7607b4afe89dfc94258f65bc0;i=848d;b=d4411d7773384d2bb902ba6b4402c1c8;m=57f53108;t=569812d969635;x=bd4f4454726706dc kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1567550 has been marked as a duplicate of this bug. ***
*** Bug 1567551 has been marked as a duplicate of this bug. ***
deja-dup-38.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
Similar problem has been detected: this error shows up after every reboot reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=09baca93910c4614a5bd4914842c237b;i=39642;b=29d530e0e68d42408ec54286aecd68b3;m=13fc2a1;t=569e0ffcff278;x=754f6858141d1615 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Just booting into Fedora 27 after a recent update to kernel reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=c01e6d9b187d407eaa22cfa287d53a7a;i=4184c;b=01a3b0317f664c1c8c4a6cd545692997;m=4482dc9;t=5695762792311;x=d06a2a2166af5088 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happens after a clean bootup and is reported after an initial login to my user account. Not every time but probably 5 or 6 times since I first noticed. I think it first started occuring with the 4.15.13-300.fc27.x86_64 release or perhaps after 4.15.14 but it still occurs with 4.15.15 reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=0efd710035ed45acaf355b63a3a524f3;i=156c17;b=a992eccc99a44122be077d4719d8a3c1;m=3423a1f;t=569608736e829;x=fc43de73c7283ce9 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1001
Similar problem has been detected: Happens on every login reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=21529d495209423a9a344ebf13d27797;i=3efc9;b=d8a4f831ba404c368dabce1c8ebc6318;m=1b84885;t=56992ddf87610;x=63d5fa7c860b446f kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1568198 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Started happening after I installed deja-dup. The backup monitor error message is displayed upon login every time. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=6cc7c20a5f2042bbbd6384c87648a26e;i=4685;b=217fbc14d49b41e4b5ac3da68fa26b1a;m=70032f1;t=569d90980941f;x=21bb89fc4800b438 kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Happened on login reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=0d66fdf1023c4f6c97f299e96b3a3d8d;i=702cc;b=f16a642093c949d7952cd134c429a585;m=e95175;t=5694c30974e5a;x=933611cf8ef64e60 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1001
Similar problem has been detected: When it's time to make a backup (past backup date), it will crash on system start and won't make backup. backup is set to be stored to remote sftp server unencrypted. backup by hand works fine. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=49c86f717ada4e69a236d34666f8f96d;i=30b506;b=5ec074b8df004a5cb8aeae739d9ecfd0;m=2e72a86;t=56a07fdd5a473;x=4e7a34c61ef978bf kernel: 4.15.16-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Its a good question. Perhaps when the machine go to sleep... Sory for my bad english language. So, Evolution and firefox are open. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=16feaf31af1c4f95a706713b6c41fb1d;i=35aa;b=0205ff3552db4aa099b6e7fceb1947d4;m=a48fdd8;t=569dc4641b490;x=82f3c8587a4810dc kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1001
Similar problem has been detected: Happens on login reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=46495e9877d940d8a7ddfad3eef9aa3b;i=17a3a;b=67fee078e409496a852f87ee1165c188;m=2d99c51;t=56a0e7e97165a;x=60ea78dc4ad5cd41 kernel: 4.15.16-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: After login, when samba share with my backups wasn't ready yet. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=4a6a24389002423aa3cb3f08e6d2125f;i=2d2be;b=d2f40123eeab415ba717f0b8b299a3a3;m=237161d;t=56a0f09dbf024;x=ab30ed95db349948 kernel: 4.15.16-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I powered on my laptop. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=67aebb5fa8a04720b1fbd5ff6f76678e;i=1d53e;b=0df2703f80f74757afff2b3cf949184c;m=5228867;t=56a1f0d497f01;x=826787acfe61f4bd kernel: 4.15.17-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 5040
*** Bug 1569035 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Happens on boot up only reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=618b7e6f755b4042ac94f9c93b4f3e49;i=d2c;b=9d048135021b41a592458cfb43a8e4f4;m=3762ff4;t=569eebac9281c;x=ba13229d30b5c92a kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: new boot and log-in reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=845bc20350d74e57b2d3eb9c8094d5b5;i=e9376;b=b3da7032b5164235a39f148e33d1aeff;m=3117637;t=56a2ef2a1509b;x=6a829f1adbc6b99e kernel: 4.15.17-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: restart the laptop reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=8a1d47df496e4f21b5609ef1cd5856e9;i=1bcda4;b=79cac74f39ac4adebfc892a51e5de9f5;m=31f60ee;t=569a27101a008;x=80b9348cd5e9414f kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 3426
Not in f27 updates yet, https://bodhi.fedoraproject.org/updates/FEDORA-2018-b2f39cabc4 was obsoleted by https://bodhi.fedoraproject.org/updates/FEDORA-2018-e32b411643 (deja-dup-38.0 rebase)
Similar problem has been detected: Battery empty, notebook shutdown, restart notebook. After logging in, problem appears reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=96b7d11c9d414797a1aaaef796a92522;i=1e27;b=c393cc9c0b3a47fca9c48488a5e8dfe6;m=272d9da;t=56a35bd4b1feb;x=a22ee6226a768453 kernel: 4.15.16-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
deja-dup-38.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
Similar problem has been detected: The backup monitor (Backup/DejaDup) started crashing on login after I set up a multi seat environment using `loginctl attach ...`. I'm not sure if there is any actual problem, I just get a notification about the backup monitor crashing. In a few days I'll now for certain if this actually affects the automatic backup schedule. Steps: 1. Install two GPUs 2. Create a second seat by doing `loginctl attach seat-1 <second-GPU-ID>` 3. Reboot and login as normal. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=4d83833e5d824a23988d58f142b3982e;i=2b622a;b=d8eefd7b14414a24be1781b2bb64ec9c;m=9ab2fbaf;t=56a49c70c6413;x=dc23c178d5bdae8 kernel: 4.15.17-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Automated backup job, once a week, backup monitor 'drops out' about once every 24-hours. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=a550deecdf5b47e7890425b36486de6f;i=acc6;b=cc9ee78095884822b0118ef7fc70fb96;m=5befa7c;t=5699775d3dcad;x=6451cd53e7d2dfa2 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Message appears after logging into Fedora 27 desktop. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=498793c738af4b159bfe32c05476ffcb;i=289ac7;b=cebbbb4bffe64007acc156cd5beede08;m=7fd6de5;t=569f7fe03bb24;x=4ac3cdde77ef9026 kernel: 4.15.14-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
(In reply to Roger Wells from comment #55) > Similar problem has been detected: > > Happens during logging into gnome desktop, on both Wayland & Xorg. > Enter password and a few seconds after desktop is created the oops message > appears > > reporter: libreport-2.9.3 > backtrace_rating: 4 > cmdline: /usr/libexec/deja-dup/deja-dup-monitor > crash_function: Gigacage::<lambda()>::operator() > executable: /usr/libexec/deja-dup/deja-dup-monitor > journald_cursor: > s=597b8ec3e33942338c319ff863324367;i=2066ea; > b=50648eb6e9ae4e1c9bde51a1e9f51590;m=2445e10;t=569a6157c5503; > x=2d48644d0abc6861 > kernel: 4.15.14-300.fc27.x86_64 > package: deja-dup-37.1-1.fc27 > reason: deja-dup-monitor killed by SIGSEGV > rootdir: / > runlevel: N 5 > type: CCpp > uid: 1000 After routine update on 4/20/18 which included an update to deja-dup the problem appears to be resolved, at least on Wayland (I'll report back if it is not resolved on Xorg, unlikely) deja-dup-38.0-1.fc27.x86_64 uname -r: 4.15.17-300.fc27.x86_64
Similar problem has been detected: Just logged in. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=cdbcc7ce4f8b478b8bb3d3e14e0b75c7;i=1322d2;b=5e1088fa32f1488690f7b579c0a1175c;m=1d5123d5;t=569cb109e1a34;x=b81cf8159a1f61ac kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: This happened at starup/login. No other action was performed. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=2a0bbbb6e84d4727b07dc29eaf87e070;i=e3c2cbb;b=69de0eb587464742b4852971ce53a3bf;m=713638d;t=56ad7c905d728;x=ae922b6638458cc kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: happened when I turned on the notebook reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/deja-dup/deja-dup-monitor crash_function: Gigacage::<lambda()>::operator() executable: /usr/libexec/deja-dup/deja-dup-monitor journald_cursor: s=d7e8305a286f4961be5130d50c59f386;i=72e;b=7bd4468c639b462bb91fa76c78a2431e;m=17fbd72;t=56a3647e234fc;x=a68e7d3cdb3c7153 kernel: 4.15.15-300.fc27.x86_64 package: deja-dup-37.1-1.fc27 reason: deja-dup-monitor killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1113
deja-dup-37.1-4.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.