Bug 1567654

Summary:	Deja-dup-monitor fails to start
Product:	[Fedora] Fedora	Reporter:	Knud Christiansen <knud.skrald>
Component:	deja-dup	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	26	CC:	fedora, gwync, jitesh.1337, kengert, walter.pete
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-15 20:17:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Knud Christiansen 2018-04-15 19:42:04 UTC

Description of problem:
Deja-dup-monitor fails to start due higher virtyel memory requirement than ulimit in script allows

Version-Release number of selected component (if applicable):
37.1.-1.fc26 x86_64

How reproducible:
allways, just install

Steps to Reproduce:
1.
2.
3.

Actual results:
journalctl shows that deja-dup-monitor crash at start up

Expected results:
Deja-dup-monitor runs

Additional info:
Ulimit in /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop is set to 1G virtuel mem limit
Actual virt. mem usage is 96G, so increasing ulimit to 100G makes it run.
Same problem in a updated F27 system.
In a F27 system which is not updated since 21 days deja-dup-monitor works and has virt mem usage of 864 MB

Comment 1 Knud Christiansen 2018-04-15 20:17:23 UTC


*** This bug has been marked as a duplicate of bug 1553945 ***