[Nssbackup-team] [Bug 588578] Re: Email notification/reporting doesn't work with GMAIL

2011-02-15 Thread BlueLight
Hi Jean-Peer,
thanks for the release 0.11.4 and the fix for gmail accounts. I noticed that 
when I try to use port 465 for smtp which is Googles preferred port sbackup 
simple hangs and I have to kill it. If I use port 587 it works fine.
in both cases TLS enabled.

The Blue Light team

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

Title:
  Email notification/reporting doesn't work with GMAIL

___
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


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

2011-01-10 Thread BlueLight
The timed backups with crom like 0 4 * * * work but without notification
icon and no emails sent

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

2011-01-10 Thread BlueLight
log file sbackup

** Attachment added: log file sbackup
   
https://bugs.launchpad.net/sbackup/+bug/697654/+attachment/1790124/+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/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 696183] Re: Failed to set GID to `admin`: 'getgrnam(): name not found: admin'

2011-01-04 Thread BlueLight
Hourly backups run fine now. No notification icon like in Ubuntu but the
backups look ok.

-- 
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/696183

Title:
  Failed to set GID to `admin`: 'getgrnam(): name not found: admin'

___
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 696183] Re: Failed to set GID to `admin`: 'getgrnam(): name not found: admin'

2011-01-03 Thread BlueLight
There have been some upgrades recently (D-Bus) . I am watching it the
next couple of days if it works now. First test looked good :-)

-- 
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/696183

Title:
  Failed to set GID to `admin`: 'getgrnam(): name not found: admin'

___
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 696183] [NEW] Failed to set GID to `admin`: 'getgrnam(): name not found: admin'

2011-01-01 Thread BlueLight
Public bug reported:


I installed sbackup on Mint LMDE from source and the installation went fine 
with all dependencies are met.
When I run it it terminates with this output.
Can someone help me to solve this?
I am using sbackup 0.11.3 on debian testing 32 bit released as Mint LMDE with 
Gnome Desktop 2.30

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-svbPHNU1wD,guid=c13e95357232396f24a87f5a003e
 DBUS_SESSION_BUS_PID=2183
drop privileges: running as nobody/nogroup
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'

** 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/696183

Title:
  Failed to set GID to `admin`: 'getgrnam(): name not found: admin'

___
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] [Question #137333]: 2010-12-10 20:32:50, 936 - INFO: SBackupdDBusObject is being terminated.

2010-12-16 Thread BlueLight
Question #137333 on Simple Backup changed:
https://answers.launchpad.net/sbackup/+question/137333

BlueLight posted a new comment:
Nobody any idea?

-- 
You received this question notification because you are a member of
Simple Backup Maintainers, which is an answer contact for Simple 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] [Question #137333]: 2010-12-10 20:32:50, 936 - INFO: SBackupdDBusObject is being terminated.

2010-12-10 Thread BlueLight
New question #137333 on Simple Backup:
https://answers.launchpad.net/sbackup/+question/137333

I installed sbackup on Mint LMDE from source and the installation went fine 
with all dependencies are met.
When I run it it terminates with this output.
Can someone help me to solve this?
I am using sbackup 0.11.3 on debian testing 32 bit released as  Mint LMDE

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-svbPHNU1wD,guid=c13e95357232396f24a87f5a003e
DBUS_SESSION_BUS_PID=2183
drop privileges: running as nobody/nogroup
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'


-- 
You received this question notification because you are a member of
Simple Backup Maintainers, which is an answer contact for Simple 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 622496] Re: problem occurs if nssbackup is run with the destination drive not present. It looses the config info.

2010-10-10 Thread BlueLight
Since sbackup and later nssbackup and much later nsbackup has been
developed with a normal user in mind (as far as I understood) and since
it deal with backups which I consider a VERY important thing to have an
unnoticed backup failure needs to be avoided under any circumstances.
For technicians like me to be called in if a user looses a config file
is bothersome because it might be my mother-in-law or many other people
whom I want or don't want to see too often.

If a backup is started or scheduled and it can't find the destination
drive it should come up with a clear big red flashing warning and give
the user a precise information what to do. And in case that doesn't
happen not to loose the config file. A backup that is saved by default
on the same harddrive is not a backup if that harddrive crashes.

I don't feel compfortable to configure Ubuntu machines with nssbackup
when I know that the config file can be lost. External drives as Igor
points outs rightly is the prefered backup medium for many Desktop users
and all Notebook and laptop users. I believe that that is reason enough
to take this issue further in the programming and find a solution.

-- 
problem occurs if nssbackup is run with the destination drive not present. It 
looses the config info.
https://bugs.launchpad.net/bugs/622496
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.

___
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 622496] Re: problem occurs if nssbackup is run with the destination drive not present. It looses the config info.

2010-10-10 Thread BlueLight
I mean barinov2000 not Igor.

-- 
problem occurs if nssbackup is run with the destination drive not present. It 
looses the config info.
https://bugs.launchpad.net/bugs/622496
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.

___
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 622496] [NEW] problem occurs if nssbackup is run with the destination drive not present. It looses the config info.

2010-08-22 Thread BlueLight
Public bug reported:

(Not So) Simple Backup Suite 0.3.1
Lucid 10.04 32 bit fully updated

When nssbackup is used with an external usb hardrive a problem occurs if 
nssbackup is run with the destination drive not present. It falls back to the 
default /var/backup directory. 
If on the next backup the usb drive is present it doesn't switch back to the 
custom destination directory but keeps the default.

I would expect nssbackup to check for an external destination (network
or usb) and use it if present.What happen if I change the default
destination directory to the usb drive? Where to do this?

** Affects: nssbackup
 Importance: Undecided
 Status: New

-- 
problem occurs if nssbackup is run with the destination drive not present. It 
looses the config info.
https://bugs.launchpad.net/bugs/622496
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.

___
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 616497] Re: Misleading option label: nssbackup is not cleaning up incomplete/corrupt backups

2010-08-16 Thread BlueLight
Hi,
I don't share Andreas statement: Of course it is easy to delete them manually 
but than the wording should be changed.

How do you delete as a normal user these corrupted files. IT's easy when
you know sudo nautilus or the shell but how many user do know that. It
is important for me to see if I have a corrupt backup but it is also
important that they are automatically removed.

If nssbackup is configured for daily backup and people just check in i
the morning for some time there is indeed a good chance that the backup
gets interrupted by a shut-down.

-- 
Misleading option label: nssbackup is not cleaning up incomplete/corrupt backups
https://bugs.launchpad.net/bugs/616497
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to nssbackup.

___
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