[Nssbackup-team] [Bug 701403] Re: Error File access manager not initialized when running as root

2011-01-12 Thread Philip Georgiev
I run also Ubuntu Maverick (10.10) 2.6.35-24-generic x86_64 and have
exactly the same problem with sbackup, otherwise a great piece of
software. I investigated the log files (with debug log level) and saw
the same entries. Today, January 12, 2010 I installed an update of
sbackup and now I have version 0.11.3ubuntu1. Unfortunately, the problem
persists.


Regards,

Philip

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/701403

Title:
  Error File access manager not initialized when running as root

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 701403] Re: Error File access manager not initialized when running as root

2011-01-12 Thread Jean-Peer Lorenz
Thank you for using SBackup and for taking the time reporting this bug.

Please take a look at following FAQ
https://answers.launchpad.net/sbackup/+faq/1324. Maybe this solves your
problem.

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/701403

Title:
  Error File access manager not initialized when running as root

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 701403] Re: Error File access manager not initialized when running as root

2011-01-12 Thread Anton
No, as I said, I can 'sudo ssh username@hostname' to my backup host
without password.

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/701403

Title:
  Error File access manager not initialized when running as root

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 701916] [NEW] Incremental Backup not working in ver. 0.11.3

2011-01-12 Thread cando
Public bug reported:

SBackup is configured to backup a local data directory on Ubuntu 10.04
(ext4) to a remote SAMBA share (Windows 7 Pro) doing every 7 days a full
backup and daily an incremental backup (simple schedule or via cron)

Same behavior when doing backup on Ubuntu 10.10 x64 of a nfs mounted
remote source to backup on local folder (both ext4).

The backup works so far, a full backup is created and sequential backups are 
marked and reported as .inc (incremental).
However the compressed files created contain always the full set of files - no 
incremental backup at all). So the file system gest blasted after a while 
because of the large backup sets.

The older version of sbackup  does work as expected, but could not
connect to SAMBA, so one has to mount the file system first and backup
to the monted folder locally.

Affected Version: Simple Backup Suite 0.11.3

I hope this can be fixed soon somehow.

kind regards cando

** Affects: sbackup
 Importance: Undecided
 Status: New

** Affects: sbackup (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Incremental Backup not working on SAMBA Target
+ Incremental Backup not working in ver. 0.11.3

** Also affects: sbackup (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
https://bugs.launchpad.net/bugs/701916

Title:
  Incremental Backup not working in ver. 0.11.3

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 701403] Re: Error File access manager not initialized when running as root

2011-01-12 Thread Philip Georgiev
Hi Jean-Peer,

I have just checked what is written in the FAQ that you pointed to. I entered 
sudo ssh username@hostname and simply connected to the remote machine. I was 
not asked to confirm anything. In both machines I have set passwords.
After that I set the remote destination in Simple Backup Config and I was able 
to connect to the remote machine. A backup was successfully created.

Thanks for your help!

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/701403

Title:
  Error File access manager not initialized when running as root

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 701403] Re: Error File access manager not initialized when running as root

2011-01-12 Thread Jean-Peer Lorenz
@Philip: that's good news.

@Anton: Did you tried the steps explained in
https://answers.launchpad.net/sbackup/+faq/1324? I'm asking since these
steps obviously helped Philip in comment #5. Do you use a passwort at
all, certificates? Thanks for your help.

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/701403

Title:
  Error File access manager not initialized when running as root

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 701916] Re: Incremental Backup not working in ver. 0.11.3

2011-01-12 Thread Jean-Peer Lorenz
Thank you for using SBackup and for taking the time reporting this bug.

In order to track down the cause of the problem some more information
are required. Please answer the following questions:

* what distribution do you use?
I've understood correctly 10.04 Lucid and 10.10 Maverick, right?

* from where was it installed (PPA, from source)?
* Is the bug reproducible; does it happen every time?
* do you run sbackup as superuser (root) or as regular user?
* Do backups (incremental) work for you, when running a backup stored on local 
drive?
* If you set up a minimal profile (maybe just a single directory) and run a 
manual backup (1st full, 2nd incr.), does it work as expected?

At first glance, your specific error looks like an underlying problem to
me (e.g. modified time stamps) not directly caused by SBackup.

Many thanks for your help.

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
https://bugs.launchpad.net/bugs/701916

Title:
  Incremental Backup not working in ver. 0.11.3

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 697654] Re: No desktop session found on Mint LMDE: no notification icon

2011-01-12 Thread Jean-Peer Lorenz
Could someone launch a backup using commandline option '--legacy-
indicator' (see https://answers.launchpad.net/sbackup/+faq/1294):

$ sbackup --legacy-indicator

and post the outcome here? Thanks.

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/697654

Title:
  No desktop session found on Mint LMDE: no notification icon

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 701759] Re: status icon not appearing in debian testing amd64

2011-01-12 Thread Jean-Peer Lorenz
*** This bug is a duplicate of bug 697654 ***
https://bugs.launchpad.net/bugs/697654

** This bug has been marked a duplicate of bug 697654
   No desktop session found on Mint LMDE: no notification icon
 * You can subscribe to bug 697654 by following this link: 
https://bugs.launchpad.net/sbackup/+bug/697654/+subscribe

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/701759

Title:
  status icon not appearing in debian testing amd64

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


Re: [Nssbackup-team] [Bug 701916] Re: Incremental Backup not working in ver. 0.11.3

2011-01-12 Thread cando
I use it on 2 different machines:

One server with Ubuntu Lucid 10.04 x64, SBackup fresh installed from ppa
One workstation Ubunty Maverick 10.10 x64, SBackup installed / upgraded 
directly from the distro package

On both machines the same error. incremental backups contain always full 
file set (ver.1.5) as stamp in file ver in backup set.

Older backups (from ver stamp1.4) were all correct, full backup set 
contains all files, incremental only changed content.

The bug is reproduceable, it happens all the time since the installation 
of the new version on both machines.

I assume Sbackup runs as root (file permissions are set to owner root).
The UI is called via: gksu sbackup-config-gtk - so it is an elevated 
user account. (after the upgrade the management UI
has completely disappeared from the System - Administration Menus and I 
have manually add the entries for
sbackup-config-gtk and sbackup-restore-gtk with elevated rights via gksu.)

related to your request: I have set up now a new profile (manual backup) 
and tried on the same disk (different directories).
It seems to work, the first set contains all files, the subsequent sets 
contain only the complete empty folder structures
(changed vs. ver. 1.4 - there were no empty folders) I have tried 
immediately following 3 backups with this configuration
and the backup seems to work.

What are the criteria how sbackup decides that one file was modified and 
needs to be backed up incrementaly?

I will  do the test tomorrow again to see, if it still works after 
reboots and clam av virus scans and I will mail you the results.

I have some questions regarding sbackup:

What happens if two sbackup jobs access the same folder / file from 
different machines (e.g. for redundancy)?
Does sbackup modify the file system on backup somehow so the two jobs 
bite each other if a user decides
to back up / copy the shared data himselve in the meantime?

Is it somewhere documented, how sbackup works and on what information it 
relies and what changes it makes to the file system?


Many thanks


cando


On 01/12/2011 05:29 PM, Jean-Peer Lorenz wrote:
 Thank you for using SBackup and for taking the time reporting this bug.

 In order to track down the cause of the problem some more information
 are required. Please answer the following questions:

 * what distribution do you use?
 I've understood correctly 10.04 Lucid and 10.10 Maverick, right?

 * from where was it installed (PPA, from source)?
 * Is the bug reproducible; does it happen every time?
 * do you run sbackup as superuser (root) or as regular user?
 * Do backups (incremental) work for you, when running a backup stored on 
 local drive?
 * If you set up a minimal profile (maybe just a single directory) and run a 
 manual backup (1st full, 2nd incr.), does it work as expected?

 At first glance, your specific error looks like an underlying problem to
 me (e.g. modified time stamps) not directly caused by SBackup.

 Many thanks for your help.


-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
https://bugs.launchpad.net/bugs/701916

Title:
  Incremental Backup not working in ver. 0.11.3

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 702121] [NEW] inflated estimate of free space needed for backup

2011-01-12 Thread weronika
Public bug reported:

When attempting a full backup, I get the error message Not enough free
space in the target directory for the planned backup (free: 922736 MiB
380 KiB, required: 1327295 MiB 489 KiB 802).  However, when I freed up
more space and ran the backup, it only took up 444G of space (according
to sudo du -sh).

In essence, this requires me to keep about 1TB of free space on my
backup drive for no reason - sbackup doesn't actually use it, but it
won't run unless all the space is there.

I have gzip compression enabled for the backups, with no splitting into
chunks.

Running Ubuntu 10.10, with sbackup 0.11.3 installed from the default repository.
(this was not a problem in Ubuntu 10.04 or earlier with previous sbackup 
versions)

** Affects: sbackup
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/702121

Title:
  inflated estimate of free space needed for backup

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 702121] Re: inflated estimate of free space needed for backup

2011-01-12 Thread weronika

** Attachment added: most recent log file
   https://bugs.launchpad.net/bugs/702121/+attachment/1792210/+files/sbackup.log

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/702121

Title:
  inflated estimate of free space needed for backup

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp


[Nssbackup-team] [Bug 697654] Re: No desktop session found on Mint LMDE: no notification icon

2011-01-12 Thread master-sonic
Here you go:
2011-01-12 19:57:09,872 - INFO: Log output for [Default Profile] is directed to 
file '/var/log/sbackup/sbackup.2011-01-12_19.57.09.871586.log'.
2011-01-12 19:57:09,872 - INFO: Profile settings are being read from file 
'/etc/sbackup.conf'.
2011-01-12 19:57:09,876 - INFO: Preparation of backup process
2011-01-12 19:57:09,876 - INFO: Initializing GIO File Access Manager.
2011-01-12 19:57:09,883 - INFO: Backup destination: 
/media/Volume-Big/Backups/sbackup
2011-01-12 19:57:09,884 - INFO: Perform tests at specified location
2011-01-12 19:57:09,895 - INFO: Checking for snapshots stored in old formats
2011-01-12 19:57:09,911 - INFO: Last full backup is fresh (1 days old )- make 
an increment
2011-01-12 19:57:09,912 - INFO: Snapshot 
'2011-01-12_19.57.09.911420.silberpfeil.inc' is being made.
2011-01-12 19:57:09,912 - INFO: Setting Base to 
'2011-01-12_19.55.55.484749.silberpfeil.inc'.
2011-01-12 19:57:09,913 - INFO: Setting packages File.
2011-01-12 19:57:10,017 - INFO: Setting Excludes File.
2011-01-12 19:57:10,017 - INFO: Setting compression format to `none`
2011-01-12 19:57:10,018 - INFO: Option 'Follow symbolic links' is disabled.
2011-01-12 19:57:10,018 - INFO: Inspect file system and collect file infos
[ ... ]
2011-01-12 19:57:26,665 - INFO: Summary of backup
2011-01-12 19:57:26,665 - INFO: Number of directories: 9518.
2011-01-12 19:57:26,665 - INFO: Total number of files: 91543.
2011-01-12 19:57:26,666 - INFO: Number of symlinks: 3130.
2011-01-12 19:57:26,666 - INFO: Number of files included in snapshot: 31.
2011-01-12 19:57:26,666 - INFO: Number of new files (also included): 6.
2011-01-12 19:57:26,666 - INFO: Number of files skipped in incremental 
snapshot: 91512.
2011-01-12 19:57:26,667 - INFO: Number of items forced to be excluded: 75.
2011-01-12 19:57:26,667 - INFO: Number of items to be excluded by config: 959.
2011-01-12 19:57:26,667 - INFO: Maximum free size required is '10 MiB 703 KiB 
409'.
2011-01-12 19:57:26,668 - INFO: Available disk size is '1650412 MiB 484 KiB'.
2011-01-12 19:57:26,687 - INFO: Snapshot is being committed
2011-01-12 19:57:26,708 - INFO: Launching TAR to make incremental backup.
2011-01-12 19:57:30,729 - INFO: Leading '/' from member names were removed.
2011-01-12 19:57:30,729 - INFO: TAR returned a message: Total bytes written: 
17643520 (17MiB, 4.3MiB/s)
2011-01-12 19:57:30,729 - INFO: TAR has been finished successfully.
2011-01-12 19:57:30,810 - INFO: Logarithmic purging
2011-01-12 19:57:30,811 - INFO: Logarithm Purging [Last week]
2011-01-12 19:57:30,812 - INFO: Logarithm Purging [Last month]
2011-01-12 19:57:30,813 - INFO: Logarithm Purging [Last year]
2011-01-12 19:57:30,816 - INFO: Logarithm Purging [2nd last year]
2011-01-12 19:57:30,817 - INFO: Logarithm Purging [remaining years]
2011-01-12 19:57:30,832 - INFO: Backup process finished.
2011-01-12 19:57:30,843 - INFO: Terminating GIO File Access Manager.
2011-01-12 19:57:30,844 - INFO: Processing of profile successfully finished (no 
errors)

2011-01-12 19:57:30,846 - INFO: SBackupdDBusObject is being terminated.
Unable to get PID of process 'gnome-session'.
Unable to get PID of process 'ksmserver'.
Neither Gnome nor KDE session is running
Unable to get PID of process 'gnome-session'.
Unable to get PID of process 'ksmserver'.
Neither Gnome nor KDE session is running
Unable to get PID of process 'gnome-session'.
Unable to get PID of process 'ksmserver'.
Neither Gnome nor KDE session is running
Unable to get PID of process 'gnome-session'.
Unable to get PID of process 'ksmserver'.
Neither Gnome nor KDE session is running
D-Bus session bus launched

DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ExTzcnQcpz,guid=ff715389623e51d8e30af9610b9e
DBUS_SESSION_BUS_PID=4594
Now launching indicator application (status icon).
Unable to get KDE Session Manager: org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.kde.ksmserver was not provided by any .service files
Unable to get Gnome Session Manager: org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.gnome.SessionManager was not provided by any .service files
No DE found using D-Bus. Looking for process id.
Unable to get PID of process 'gnome-session'.
Unable to get PID of process 'ksmserver'.
Neither Gnome nor KDE session is running
No desktop session found. Indicator application is not started.
Failed to set GID to `admin`: 'getgrnam(): name not found: admin'
drop privileges: running as nobody/nogroup

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/697654

Title:
  No desktop session found on Mint LMDE: no notification icon

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp