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

2011-01-13 Thread Anton
Yes, I've gone through the steps of that FAQ. I have certificates
(pub/private key-pairs) set up, and can 'sudo ssh feenstra@backuphost'
without password. E.g.,

$ sudo ssh feenstra@backuphost uptime
 09:44:05 up 150 days,  2:56,  2 users,  load average: 0.00, 0.00, 0.00

-- 
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 697654] Re: No desktop session found on Mint LMDE: no notification icon

2011-01-13 Thread BlueLight
sbackup --legacy-indicator 21 | tee log-sbackup

here is my output:

2011-01-14 08:02:45,233 - INFO: Log output for [Default Profile] is directed to 
file '/var/log/sbackup/sbackup.2011-01-14_08.02.45.232742.log'.
2011-01-14 08:02:45,234 - INFO: Profile settings are being read from file 
'/etc/sbackup.conf'.
2011-01-14 08:02:45,237 - INFO: Preparation of backup process
2011-01-14 08:02:45,238 - INFO: Initializing GIO File Access Manager.
2011-01-14 08:02:45,244 - INFO: Backup destination: 
/media/backup/new-daily-backup-sbackup
2011-01-14 08:02:45,245 - INFO: Perform tests at specified location
2011-01-14 08:02:45,254 - INFO: Checking for snapshots stored in old formats
2011-01-14 08:02:45,257 - INFO: Corrupt snapshot 
`2011-01-14_08.01.52.920468.rolling.corrupt` found. Skipped.
2011-01-14 08:02:45,267 - INFO: Corrupt snapshot 
`2011-01-14_08.01.52.920468.rolling.corrupt` found. Skipped.
2011-01-14 08:02:45,269 - INFO: Last full backup is fresh (4 days old )- make 
an increment
2011-01-14 08:02:45,270 - INFO: Snapshot 
'2011-01-14_08.02.45.270048.rolling.inc' is being made.
2011-01-14 08:02:45,271 - INFO: Setting Base to 
'2011-01-14_08.02.13.031316.rolling.inc'.
2011-01-14 08:02:45,271 - INFO: Setting packages File.
2011-01-14 08:02:45,374 - INFO: Setting Excludes File.
2011-01-14 08:02:45,374 - INFO: Setting compression format to `bzip2`
2011-01-14 08:02:45,374 - INFO: Option 'Follow symbolic links' is disabled.
2011-01-14 08:02:45,375 - INFO: Inspect file system and collect file infos
2011-01-14 08:02:47,452 - INFO: File '/home/.
lots of files :-)

2011-01-14 08:02:52,210 - INFO: Summary of backup
2011-01-14 08:02:52,210 - INFO: Number of directories: 3266.
2011-01-14 08:02:52,210 - INFO: Total number of files: 36890.
2011-01-14 08:02:52,211 - INFO: Number of symlinks: 224.
2011-01-14 08:02:52,211 - INFO: Number of files included in snapshot: 0.
2011-01-14 08:02:52,211 - INFO: Number of new files (also included): 0.
2011-01-14 08:02:52,212 - INFO: Number of files skipped in incremental 
snapshot: 36890.
2011-01-14 08:02:52,212 - INFO: Number of items forced to be excluded: 11.
2011-01-14 08:02:52,212 - INFO: Number of items to be excluded by config: 890.
2011-01-14 08:02:52,212 - INFO: Maximum free size required is '1 MiB 721 KiB'.
2011-01-14 08:02:52,213 - INFO: Available disk size is '46646 MiB 968 KiB'.
2011-01-14 08:02:52,220 - INFO: Snapshot is being committed
2011-01-14 08:02:52,230 - INFO: Launching TAR to make incremental backup.
2011-01-14 08:02:54,170 - INFO: Leading '/' from member names were removed.
2011-01-14 08:02:54,171 - INFO: TAR returned a message: Total bytes written: 
4741120 (4.6MiB, 2.6MiB/s)
2011-01-14 08:02:54,171 - INFO: TAR has been finished successfully.
2011-01-14 08:02:54,207 - INFO: Corrupt snapshot 
`2011-01-14_08.01.52.920468.rolling.corrupt` found. Skipped.
2011-01-14 08:02:54,209 - INFO: Simple purge - remove freestanding snapshots 
older than 7 days.
2011-01-14 08:02:54,213 - INFO: Corrupt snapshot 
`2011-01-14_08.01.52.920468.rolling.corrupt` found. Skipped.
2011-01-14 08:02:54,215 - INFO: Backup process finished.
2011-01-14 08:02:54,221 - INFO: Terminating GIO File Access Manager.
2011-01-14 08:02:54,221 - INFO: Processing of profile successfully finished (no 
errors)

2011-01-14 08:02:54,223 - 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-1FLr28qFJR,guid=19577d2cb3beb0e1611c86eb0584
DBUS_SESSION_BUS_PID=4478
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