GConf error when run as cronjob

Bug #335450 reported by Justin Painter
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
sbackup (Ubuntu)
Expired
Undecided
Unassigned
simplebackup (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: simplebackup

Running sbackup as cronjob on Ubuntu 8.10 results in the following error message:

/etc/cron.daily/sbackup:
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)

Google turned up this page about a similar error:
http://stackoverflow.com/questions/257658/how-can-i-make-a-fake-active-session-for-gconf

Applying the same fix mentioned there to the /usr/share/sbackup/sbackup bash script fixed the problem on my system. Patch is attached. My sbackup package version is 0.10.5ubuntu2.

Revision history for this message
Justin Painter (hpainter) wrote :
Changed in simplebackup (Ubuntu):
status: New → Invalid
Revision history for this message
primal23 (ddurgan32) wrote :

Patch did not work for my system.

Revision history for this message
click (daniel-zhelev) wrote :

This bug still persist!

Linux yorkfield 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux
root@yorkfield:~# dpkg -i | grep sbackup

ii sbackup 0.10.5ubuntu2.1 Simple Backup Suite for desktop use

Running sbackup script (/etc/cron.daily/sbackup) from shell as root seems to work. Backups are written even with this error e-mailed by root suggested fix is applying

eval `dbus-launch --sh-syntax`

export DBUS_SESSION_BUS_ADDRESS
export DBUS_SESSION_BUS_PID

to /etc/cron.daily/sbacjup

As I can see this bug is marked as "New" from 2009? Great... is there will be any fix somewhere around 2020?

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Thank you for your comment.

Could you please describe how this bug/issue affects you when using sbackup? Do backups actually work or don't they? It's not entirely clear to me what the exact reported problem is. Moreover, could you please provide steps how to reproduce the issue on your system? Does this happen all the time, periodically...? Please add your log output or terminal output.

Thanks for your help.

P.S.: Please avoid further statements such as "Great... is there will be any fix somewhere around 2020?". This is a community driven project and its future depends solely on valuable contributions and fixes from volunteers. So, please contribute with helpful bug reports etc. At least, please respect the work of others. Thanks.

Changed in sbackup (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for sbackup (Ubuntu) because there has been no activity for 60 days.]

Changed in sbackup (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.