Comment 10 for bug 1087872

I have actually done that (changed the permissions), or to be more precise
- I believe that I have done that.

To follow-up on what you say, I have "root" privileges. So I am both
ADMINISTRATOR and USER at the same time.

1. Through my "root" privileges I can schedule the Administrative version
to run at specific times.

2. Both the ADMINISTRATIVE version and USER version have slightly different
default profiles. I may be misunderstanding how the default profiles should
be set-up between the two versions.

3. When the ADMINISTRATIVE version has a scheduled back-up, I am unclear as
to whether the USER version should also be executing. It appears that it
does, so there may be a conflict. I have "root" privileges and I am also
am the USER at the same time.
    By coincidence, as I am writing this, I received the error message
below from "cron". Also see #4 below. The error message would seem to imply
that the ADMINISTRATIVE version was "rejected" from executing.
    -------------------------------------------
    "Backup is not being started.
     "Another application instance is already running. "
    ----------------------------------------------

4. The current back-up (from #3) appears stuck at 98.6% for the past 2
hours. Based on the incomplete log generated so far, it would appear that
the USER version executed, but that is now "stuck". I will let it run and
see what happens. That would seem to imply that the error message mentioned
in #3 fro, "cron" would apply to rejecting the ADMINISTRATIVE version from
running.

On Sat, Dec 29, 2012 at 4:29 AM, Anton <email address hidden> wrote:

> Just chiming in with a suggestion here, not sure if it will help.
>
> Could it be that when you run the backup as user, it fails to be able to
> read the contents of the backup file because they are owned by root,
> because (one of) the previous backup(s) was (were) made by root? And
> this read-error is not caught?
>
> If you can check dir and file ownerships and permissions in your backup
> location, you could fix it with chown and try again to see if that
> solves it for you.
>
> Jean-Peer any chance you could get these .desktop file patches that make
> the root sbackup appear different from the user ones, pushed into the
> repositories?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1087872
>
> Title:
> Backup to Remote PC Freezes
>
> Status in sbackup:
> New
>
> Bug description:
> Using Ubuntu 12.10 attempting to backup to a remote WindowsXP computer
> Have AMD-64 bit Ubuntu
> sbackup-gtk 0.11.4-0ubuntu4
> installed from Ubuntu directly
>
> String to access remote computer: smb://sabre/Storage/Backup_Altair
>
> manually the backups seems to work correctly
> However the automated mackup using Gnome Shcduler only works
> sporadically.
>
> I just received error message "File access manager not initialized"
> Aslo get an error message that Ubuntu has had an "internal error".
> Then Ubuntu asks if I am attempting to connect to a remote computer,
> which I am.
> sbacckup "freezes" stays stuck in assembling files.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions
>