Description of problem: When logging into a new session deja-dup-monitor crashes reproduceable. Starting deja-dup-monitor from a terminal emulator has the following result: $ sh -c "ulimit -v 1000000; exec /usr/libexec/deja-dup/deja-dup-monitor" FATAL: Could not allocate gigacage memory with maxAlignment = 34359738368, totalSize = 120259084288. Speicherzugriffsfehler (Speicherabzug geschrieben) Version-Release number of selected component (if applicable): $ rpm -q deja-dup deja-dup-37.1-2.fc28.x86_64 How reproducible: allways Steps to Reproduce: 1. Make sure deja-dup is installed 2. Log out from your gnome session 3. Log into a new gnome session Actual results: deja-dup-monitor crashes at startup Expected results: Additional info: Removing the memory-limitation seems to fix the startup crash
This limit is in place to mitigate: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1302416 This should be copying the file from /etc/xdg/ to your .config/autostart/ Try removing the limit there, and see if you hit the bug from 1302416.
Also affects Fedora 27: $ rpm -q deja-dup deja-dup-37.1-1.fc27.x86_64 I cannot understand which operation mentioned in Comment #1 should I perform, though. I have a org.gnome.DejaDup.Monitor.desktop in /etc/xdg/autostart, but not in ~/.config/autostart/.
*** Bug 1567654 has been marked as a duplicate of this bug. ***
(In reply to Andrea Vai from comment #2) > Also affects Fedora 27: > > $ rpm -q deja-dup > deja-dup-37.1-1.fc27.x86_64 > > I cannot understand which operation mentioned in Comment #1 should I > perform, though. I have a org.gnome.DejaDup.Monitor.desktop in > /etc/xdg/autostart, but not in ~/.config/autostart/. BTW, manually invoking deja-dup-monitor: $ /usr/libexec/deja-dup/deja-dup-monitor works for me.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.