Only folders backed up

The errors about chgrp may appear if your backup file system is not a linux one: like NTFS or FAT.

The command to make the backup is:
rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/media/FREECOM HDD" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/media/FREECOM HDD/backintime/new_snapshot/backup/"

What you can do i create a folder "ABC" on your USB Drive and try the command manually:
rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/media/FREECOM HDD" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/media/FREECOM HDD/backintime/ABC"

Can you please check the output ?
Does it work like this ?

Hi - thanks for getting back.

If I understand your request, you meant this:
1. Create ABC folder on root of external drive.
2. Enter the command shown.
That's what I did and this is the output from step 2:

= = = = = = = = = = = = = = =
reler@linux-tx7g:~> rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/media/FREECOM HDD" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/media/FREECOM HDD/backintime/ABC"
sending incremental file list
created directory /media/FREECOM HDD/backintime/ABC
./
home/
home/reler/
rsync: chgrp "/media/FREECOM HDD/backintime/ABC/home/reler" failed: Operation not permitted (1)
home/reler/BBR/
rsync: chgrp "/media/FREECOM HDD/backintime/ABC/home/reler/BBR" failed: Operation not permitted (1)
home/reler/BBR/bit_test/
rsync: chgrp "/media/FREECOM HDD/backintime/ABC/home/reler/BBR/bit_test" failed: Operation not permitted (1)
home/reler/BBR/bit_test/test.txt
rsync: rsync_xal_set: lsetxattr("home/reler","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/ABC/home/reler" failed: Operation not permitted (1)
rsync: rsync_xal_set: lsetxattr("home/reler/BBR","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/ABC/home/reler/BBR" failed: Operation not permitted (1)
rsync: rsync_xal_set: lsetxattr("home/reler/BBR/bit_test","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/ABC/home/reler/BBR/bit_test" failed: Operation not permitted (1)
rsync: mkstemp "/media/FREECOM HDD/backintime/ABC/home/reler/BBR/bit_test/.test.txt.WdtA7l" failed: Operation not permitted (1)

sent 585 bytes received 56 bytes 1282.00 bytes/sec
total size is 13 speedup is 0.02
rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2]
reler@linux-tx7g:~>
= = = = = = = = = = = = = = =

Oh, and the partitioner tool reports the external drive's file system as "Win95 FAT32". What puzzles me is why this should work on Ubuntu 9.04, but fail on SuSe. On both, I have the NTFS file hadnling set up and can read and write from NTFS volumes - I may be wrong, but I thought that would also mean that other MS-style formats could be handled too.

One other thing that occurs to me is that if I recall, my OpenSuse kernel is 2.25 (???) and the Ubuntu system is later - 2.26 at least. I will just check those facts now and update again.

Thanks for your assistance.

Reler

OK - just checked as promised ...

Just been back on to my Ubuntu system - took another snapshot and experimented with restoring deleted files. Absolutely no problem, so the file system question may be irrelevant. However, if it's something in the kernel, there is a difference ...

- OpenSuse kernel: 2.6.25
- Ubuntu kernel: 2.6.28

Hope this helps.

Reler

It is not a kernel issue, but it looks like a permissions issue after all,
but not one that is as easy to solve as going for root, as it is not allowed
to do anything on your external harddisk.
Can you pass us the output from the next command:
grep FREECOM /etc/fstab

What worries me is that your partioner says that it is FAT32 while you say
that it is a NTFS disk. You did not mount it as a NTFS while it is a FAT32
disk, did you?

2009/11/18 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> reler gave more information on the question:
> OK - just checked as promised ...
>
> Just been back on to my Ubuntu system - took another snapshot and
> experimented with restoring deleted files. Absolutely no problem, so the
> file system question may be irrelevant. However, if it's something in
> the kernel, there is a difference ...
>
> - OpenSuse kernel: 2.6.25
> - Ubuntu kernel: 2.6.28
>
> Hope this helps.
>
> Reler
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

Hi Bart - grep FREECOM /etc/fstab just returns the prompt - no output at all. So I looked in /etc/fstab and it has no entries for the FREECOM drive at all (whether it's powered on from boot or not). I assume that's a consistent result with the grep.

I don't think that I said that the external drive is an NTFS disk, though you could clearly infer that from what I wrote earlier - I should have made that clearer, sorry.

I mentioned NTFS because this machine does have a second internal drive that *is* NTFS-partitioned. I can read and write to that fine using ntfs3g under both flavours of Linux. Having had to wrestle a little with that when I set the machine up, I assumed (perhaps incorrectly) that it was involved in reading/writing to any MS-style file system.

The external drive had previously been used when attached to an XP laptop (and still is occasionally). I seem to recall that when I bought it, it was pre-formatted. I am a refugee from Windows, and when it came to using it on Linux, I just plugged the external drive in to a USB port and seemed to be in business. I *never* mount it explicitly. I can also create files on the FREECOM drive from both Suse & Ubuntu with no problems. It's just when BackInTime under Suse tries it that I get the issues described.

If it is down to permissions, what I find weird is that it can create folders but not files. But maybe that's because I don't know enough about Linux !

Hope this helps - any ideas ?

Regards,

Reler

Just type "mount" or "cat /etc/mtab" (not /etc/fstab) to see what file system is on the drive.

This is good ... I am learning a lot about Linux ! Here is the relevant line under each system (which for both commands, is the last that is shown):

OpenSuse 11.0:
mount ...
/dev/sdb1 on /media/FREECOM HDD type vfat (rw,nosuid,nodev,shortname=lower,flush,utf8,uid=1000)

cat /etc/mtab ...
/dev/sdb1 /media/FREECOM\040HDD vfat rw,nosuid,nodev,shortname=lower,flush,utf8,uid=1000 0 0

Ubuntu 9.04:
mount ...
/dev/sdc1 on /media/FREECOM HDD type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)

cat /etc/mtab ...
/dev/sdc1 /media/FREECOM\040HDD vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0

(FYI: The Ubuntu output shown above from "mount" wraps around after "vfat" on this web form.)

Does that throw any light on the problem ?

Regards

Reler

First your file system is FAT (not NTFS).
The problems with FAT is that hard-links are not supported (every snapshots will contain all the files). I suggest to use a linux filesystem (ext3/4) or event NTFS.

Then the is the real question: why it works on 9.04 and not on 9.10 ?
BIT use rsync to take snapshots. Maybe they don't have the same version.
Please run "rsync --version" on both systems.

Hi Dan - there's only one Ubuntu system involved here and it's 9.04 - the other is OpenSuse 11.0. Reformatting the drive to Linux file system is not really desirable because the removable drive is also occasionally connected to a WIndows laptop.

Anyway, Ubuntu 9.04 has rsync 3.0.5 and OpenSuse 11.0 has 3.0.2.

So is there any reason NOT to update Suse to rsync 3.0.6 ? (Which, I see is now the latest release.) I mean some kind of technical reason that makes anything beyond 3.0.2 unusable in Suse 11.0 (although I realise that this may not be your area of expertise.)

I would prefer to do this rather than an out-and-out upgrade because part of the reason for getting involved in this whole exercise was so that I could do a complete back-up prior to doing an upgrade ;-)

Thanks,

Reler

OK, well I decided to go ahead and update rsync in OpenSuse anyway so I have downloaded the source and followed the instructions at http://www.samba.org/ftp/unpacked/rsync/INSTALL i.e.
  $ ./configure
  $ make
  # make install

Sure enough, when I do rsync --version, I now see it as 3.0.6. So returning to backintime, I run my test again ... same problem ! Folders only :-(

Hmmm ... checked Yast and it says that 3.0.2 is the installed rsync package and that this is also the latest available via the usual Suse repositories fro 11.0. I wonder if backintime is still picking that up somehow, in spite of the fact that a call to rsync from the terminal shows 3.0.6 ? Just to see if it made a difference, I used Yast to uninstall and reinstall backintime. No difference.

So I have gone back to the test suggested above by Dan i.e. this one:
What you can do i create a folder "ABC" on your USB Drive and try the command manually:
rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/media/FREECOM HDD" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/media/FREECOM HDD/backintime/ABC"

The output this time was quite different than before:
rsync: ACLs are not supported on this client
rsync error: syntax or usage error (code 1) at main.c(1422) [client=3.0.6]
reler@linux-tx7g:~>

I am guessing that "ACL" is Access Control List, but beyond that, I am now lost again.

Does this help ?

Thanks again,

Reler

Sorry my mistake I meant mtab instead of fstab, Ubuntu mounts external
drives automatically without fstab rules. In 9.04 and 9.10 you do not have
to worry about NTFS read/write any longer, the distributed NTFS driver is
good for both.
Hmm you installed a package manually, I highly recommend you NOT to do that,
especially if you are still new to linux, but always use your package
installer (yast in the case of Suse, dpkg or apt(itude) for ubuntu) if
possible. There should be rpm's around for rsync for SUSE 11. Package
installers make sure all the dependencies are met and that all packages on
your system do not interfere with eachother. I guess putting the new version
of rsync in there cannot do really harm, so I think in this case there is no
damage done. Yast will show 3.0.2, because you installed it not via yast, so
yast is unaware of the new version (also in resolving dependencies for other
packages like backintime it will think that is 3.0.2!)

Ehm Dan what was the fix for the ACL support??? Compile rsync with ACL
support?

2009/11/21 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> reler gave more information on the question:
> OK, well I decided to go ahead and update rsync in OpenSuse anyway so I
> have downloaded the source and followed the instructions at
> http://www.samba.org/ftp/unpacked/rsync/INSTALL i.e.
> $ ./configure
> $ make
> # make install
>
> Sure enough, when I do rsync --version, I now see it as 3.0.6. So
> returning to backintime, I run my test again ... same problem ! Folders
> only :-(
>
> Hmmm ... checked Yast and it says that 3.0.2 is the installed rsync
> package and that this is also the latest available via the usual Suse
> repositories fro 11.0. I wonder if backintime is still picking that up
> somehow, in spite of the fact that a call to rsync from the terminal
> shows 3.0.6 ? Just to see if it made a difference, I used Yast to
> uninstall and reinstall backintime. No difference.
>
> So I have gone back to the test suggested above by Dan i.e. this one:
> What you can do i create a folder "ABC" on your USB Drive and try the
> command manually:
> rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete
> --exclude="/media/FREECOM HDD"
> --exclude="/home/reler/.local/share/backintime"
> --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/"
> --include="/home/reler/" --include="/home/" --exclude=".*"
> --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**"
> --exclude="*" / "/media/FREECOM HDD/backintime/ABC"
>
> The output this time was quite different than before:
> rsync: ACLs are not supported on this client
> rsync error: syntax or usage error (code 1) at main.c(1422) [client=3.0.6]
> reler@linux-tx7g:~>
>
> I am guessing that "ACL" is Access Control List, but beyond that, I am
> now lost again.
>
> Does this help ?
>
> Thanks again,
>
> Reler
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

Thanks Bart - I hear what you say about compiling from scratch, but I only did this after looking for rpms for rsync elsewhere. I couldn't find any for 11.0 - maybe I am looking in the wrong places ! After all, 11.0 is now two releases behind. Rest assured that when I find a way of making a good comprehensive backup, I WILL be upgrading ;-)

I understand what you say about Yast still showing 3.0.2 - I was wondering if backintime uses some kind of path that picks that up instead of 3.0.6 that I installed.

Anyway, sounds like you and Dan may now how to get around the ACL issue, so over to you Dan ...

Reler

Can you please run "rsync --version" on both systems and attach the output.
Event on the same version different distributions can use different parameters so some options are enabled/disabled.

OK, here it is:

OpenSuse 11.0
reler@linux-tx7g:~> rsync --version
rsync version 3.0.6 protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, no ACLs, xattrs, iconv, symtimes
...

Ubuntu 9.04
reler@reler-desktop:~$ rsync --version
rsync version 3.0.5 protocol version 30
Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, symtimes

Looks like ACLs are different !

Reler

Guys, I have been trying to find the right way to recompile rsync on Suse with the appropriate parameter to get to the way it is on Ubuntu.

Any ideas ?

Thanks,

Reler

For build options you can run:
./configure --help

But you raise another problem. I think BIT must use ACL/xattr only if rsync support them.
I open the bug: https://bugs.launchpad.net/backintime/+bug/489380

Dan, thanks but I am still stuck with this compilation question. (Remember, Linux newb, Windows refugee !)

I have done ./configure --help and carefully examined the output. The only part that talks about ACL is a line under the heading "Optional Features" and it says ...
  --disable-acl-support disable ACL support

Nothing about enabling it, so I guessed and ran "./configure --enable-acl-support" ... and that failed. So then, I tried "./configure --enable-acl-support=YES" and that successfully ran to completion ... BUT, towards the end of the output, I found these lines:
----------------------------
...
checking for _acl... no
checking for __acl... no
checking for _facl... no
checking for __facl... no
checking whether to support ACLs... running tests:
checking for acl_get_file in -lacl... no
checking for ACL support... no
checking ACL test results... No ACL support found
checking whether to support extended attributes... Using Linux xattrs
configure.sh: creating ./config.status
config.status: creating Makefile
config.status: creating lib/dummy
config.status: creating zlib/dummy
config.status: creating popt/dummy
config.status: creating shconfig
config.status: creating config.h
config.status: config.h is unchanged

    rsync 3.0.6 configuration successful
----------------------------

I even tried "./configure --disable-acl-support=NO" but the result was the same.

Like I said, Linux newb/Windows refugee ! The rsync doc only seems to show how to turn things like ACL off, not on ! Assuming my guess as to how to do that was correct, it doesn't seem to have worked. I know that strictly this is off-topic, but you guys must know rsync inside-out ... can you help please ?

Thanks,

Reler

I think ACL is by default autodetect.
You can try to install libacl-devel but I don't know how on OpenSUSE.

OK Dan, thanks. Now I have good news and bad news.

Good news, I found libacl-devel (version 2.2.47-6.1) in Suse's package manager and installed it. Then I recompiled rsynch without specifying any configuration options. So if I now run rsync --version, I get this:

rsync version 3.0.6 protocol version 30
...
Capabilities:
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, symtimes

... which is the same that I get on my Ubuntu 9.04 system. Good.

So let's try again ! But now we come to the bad news ! Same problem.

I started backintime-gnome using the command line and this is the output:
---------------------------
reler@linux-tx7g:~> backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

INFO: Lock
INFO: Include folders: ['/home/reler/BBR/bit_test']
INFO: Ignore folders: []
INFO: Last snapshots: {}
INFO: [GnomePlugin.Systray.run]
INFO: [GnomePlugin.Systray.run] begin loop
INFO: Call rsync to take the snapshot
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler" failed: Operation not permitted (1)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR" failed: Operation not permitted (1)
rsync: rsync_xal_set: lsetxattr("home/reler","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test" failed: Operation not permitted (1)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler" failed: Operation not permitted (1)
rsync: rsync_xal_set: lsetxattr("home/reler/BBR","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR" failed: Operation not permitted (1)
rsync: rsync_xal_set: lsetxattr("home/reler/BBR/bit_test","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test" failed: Operation not permitted (1)
rsync: mkstemp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test/.test.txt.vIV1gn" failed: Operation not permitted (1)
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/share/backintime/plugins/gnomeplugin.py", line 111, in run
    self.notification.attach_to_status_icon( status_icon )
AttributeError: 'pynotify.Notification' object has no attribute 'attach_to_status_icon'

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]
WARNING: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/media/FREECOM HDD" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/media/FREECOM HDD/backintime/new_snapshot/backup/"" returns 5888
INFO: Save permissions
INFO: Remove backups older than: 19991129-000000
INFO: Keep min free disk space: 1024 Mb
INFO: Unlock
reler@linux-tx7g:~>
---------------------------
To my eye, I seem to have some of the same errors we started with, though some have disappeared and some additional messages seem to be there.

I am just guessing here, but we did talk about ntfs earlier in this thread - is this still likely to be an issue ? I am running:
 ntfs-3g (version 1.2506-5.1)
 ntfs-config (version 1.0.1-99.1)
 ntfsprogs (version 1.13.1-80.1)

Thanks for sticking with me guys.

Reler

rsync seems OK.
Ignore group//atributes errors. NTFS don't support them but this info are saved in a special file.

The crash is in pynotify.
What is you pynotify version ?

Hi Dan - I typed "pynotify" into YaST (The OpenSuse packager manager) under the "Installed" tab and it showed "pynotify" as the package name and it reports that I have version "0.1.1-0.pm.1 (i586)".

I looked under Ubuntu but could not work out how to get that level of granularity in the reporting. All I could establish was that I was running version 2.6 of Python (under 9.04). Back in YaST, it tells me I am running 2.5.2-26.4 (i586).

Does this help ?

Reler

Well in Ubuntu it seems to be called python-notify and it is 0.1.1-2build2 in Ubuntu 9.10.
I'm not sure what can I do more.

Hi Dan - if you're confused, I'm glad of the company ;-) Ha Ha !

I have now had time to take a slightly closer look at this. From this, can I ask two things please ...

1. Just so I know, how do you get that info from Ubuntu ? I am not so familiar with its package manager. This could actually be important because ...

2. I did a little Googling, first just on "attach_to_status_icon" (which seems to be key in one of the error messages) and I found http://trac.galago-project.org/ticket/121 in which the Ubuntu team suggest that "src/pynotify.c does not get rebuilt properly".

I then Googled +"attach_to_status_icon" +Suse and found this: http://lists.opensuse.org/opensuse-commit/2009-03/msg00559.html which I think is saying something similar (though I am still down-level on all the jargon).

But noting what I wrote this morning, and the version number you report from 9.10, I'm guessing that the "2build2" part after the hyphen refers to a version that includes a rebuilt pynotify.c. I'm not sure what the number after the hyphen means, but in the Suse details reported, maybe "0.pm.1" means that this is lacking there.

So I am now wondering if this is a question of rebuilding/reinstalling python in order to get the rebuilt pynotify.c

If you guys think it's worth trying, please advise. We seem so close with this, it would be really cool to nail it !

Thanks again for all your help.

Reler

1. Synaptics is a good GUI for the package manager.
2. The code using pynotify is based on examples. I didn't find a real doc about it. What I can do is to put try/except around attach_to_status_icon.

Hi Dan - this in haste ....

1. Thanks.
2, I'm sorry, I don't understand what you mean. Are you asking me to do something ? If so, what, exactly ?

Thanks again,

Reler

Just returned and reviewed the last message I left. It looks like I may have accidentally signalled that the problem was solved. If so, that was a mistake - sorry.

Further clarification on Dan's last remark: Dan, I don't understand your response in point 2 and am unclear if you are suggesting whether I should do anything (and if so what).

Thanks,

Roger

2. It is not a question, it is a fact. I didn't find a doc about how to use pynotify so the code is based on examples I found on the web. Maybe I'm not using as it should be but I didn't found how it should be. What I did is adding try/except around 'attach_to_status_icon' (this is where it crush in your last test).

I fixed the bug about ACL/xattr. Now BIT tries to detect if rsync support them.

Thanks for the update Dan - I'm really sorry, I find it hard to understand some of the jargon here. Remember, I am not a hard-core Linux techie, I am still learning ;-)

Reading your last two posts, you seem to be suggesting that you have put something in the code for BIT that tests for something ("try/except" ?) as it is about to hit the "attach_to_status" that causes my last reported problem. Presumably the idea was to allow you to narrow things down. But you haven't said what the result of that test was or what conclusion can be drawn from it.

You started talking about this "try/except" when I posted that I had found references to the code for pynotify.c not being rebuilt properly for the python build. Given my inexperience, I don't understand how that relates to the "try-except", so I am still wondering if this is a question of recompiling or reinstalling python so as to get the recompiled pynotify.c in to it.

This question has shown up a bug which you've fixed which is great, but I still have a problem. The problem "feels" close to a solution so I'm just wondering how this can be moved forward. I've posted all the output but if there's anything more you need, or anything that you think I can try, please let me know.

Thanks,

Reler

I can't test it since I run Ubuntu :)
The try/except around attach_to_status_icon (python report that this don't exists on your OpenSuse 11.0 system) should prevent the crash. Instead of crash the call will be ignored.
I don't know how you can build pynotify to include this method but since the standard included in OpenSuse don't have it, BIT should not crash.

But it does ! Other Suse users seem to be using it successfully, so it seems that this is actually about the pre-requisites for running BIT successfully

Maybe I am misunderstanding what you're trying to tell me ... I know you guys are the experts, and that I'm not using your OS, but as far as I can see, Ubuntu is NOT one of those pre-reqs. Is there a formal list of pre-reqs for BIT ? If so, I can check my system to see if something is missing.

Alternatively, because this link (http://linux.softpedia.com/get/Programming/Libraries/notify-python-37156.shtml) suggests to me that my version of pynotify DOES have attach_to_status in it, then maybe the problem IS in the way it's coded.

And finally, can you address my questions about the links that I have posted that seem to point to an issue that's related to the current problem - they seem to have been forgotten about. Likewise whether recompilation would help.

And again ... how we can move this forward ? After all, Suse people ARE using BIT and whether Suse or Ubuntu, they're BOTH Linux systems - all I'm trying to do is work out what the right environment is for BIT to work.

With thanks in anticipation,

Reler

I don't use OpenSUSE and I don't know how to create packages for it. You should search on OpenSUSE forums. Maybe someone has the same problem as you and he may have a solution. I can hope that the fix I commit work, but you have to wait for the next release.

Hey Reler,
I had a look at your last log: BiT and rsync appears to be OK actually
mounting is I think the problem.
2 things we might have to now: the UID of refer is in both cases 1000?
and what is the output for
ls -als "/media/FREECOM HDD/backintime/"
on both systems?

Cheers,
Bart

2009/12/3 Dan <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> Status: Open => Answered
>
> Dan proposed the following answer:
> I don't use OpenSUSE and I don't know how to create packages for it. You
> should search on OpenSUSE forums. Maybe someone has the same problem as
> you and he may have a solution. I can hope that the fix I commit work,
> but you have to wait for the next release.
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

Hi Bart. I did as you asked and this is the output ...
-----------------------------------------
OpenSuse 11.0
reler@linux-tx7g:~> ls -als "/media/FREECOM HDD/backintime/"
total 96
32 drwxr-xr-x 3 reler root 32768 2009-11-29 12:01 .
32 drwxr-xr-x 29 reler root 32768 1970-01-01 01:00 ..
32 drwxr-xr-x 3 reler root 32768 2009-11-29 12:01 20091129-120101
reler@linux-tx7g:~>
---------------
Ubuntu 9.04
reler@reler-desktop:~$ ls -als "/media/FREECOM HDD/backintime/"
total 96
32 drwx------ 3 reler root 32768 2009-11-29 12:01 .
32 drwx------ 29 reler root 32768 1970-01-01 01:00 ..
32 drwx------ 3 reler root 32768 2009-11-29 12:01 20091129-120101
reler@reler-desktop:~$
-----------------------------------------

Another difference - All right ! This is where my knowledge of Linux is shaky: I understand that this is to do with permissions, so I defer to you as how to deal with this. (Would it be a "chmod" ? Is that the one ?)

I have to say it puzzles me slightly in that logged in to Suse, I have no problem reading from or writing to the FREECOM device.

Hope that helps.

Thanks :-)

Reler

OK that looks good now the same trick for:
ls -als /home/reler/BBR

Might have nothing to do with your errors, but I do not get the operation
not permitted errors...

Cheers,
Bart

2009/12/3 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> Status: Answered => Open
>
> reler is still having a problem:
> Hi Bart. I did as you asked and this is the output ...
> -----------------------------------------
> OpenSuse 11.0
> reler@linux-tx7g:~> ls -als "/media/FREECOM HDD/backintime/"
> total 96
> 32 drwxr-xr-x 3 reler root 32768 2009-11-29 12:01 .
> 32 drwxr-xr-x 29 reler root 32768 1970-01-01 01:00 ..
> 32 drwxr-xr-x 3 reler root 32768 2009-11-29 12:01 20091129-120101
> reler@linux-tx7g:~>
> ---------------
> Ubuntu 9.04
> reler@reler-desktop:~$ ls -als "/media/FREECOM HDD/backintime/"
> total 96
> 32 drwx------ 3 reler root 32768 2009-11-29 12:01 .
> 32 drwx------ 29 reler root 32768 1970-01-01 01:00 ..
> 32 drwx------ 3 reler root 32768 2009-11-29 12:01 20091129-120101
> reler@reler-desktop:~$
> -----------------------------------------
>
> Another difference - All right ! This is where my knowledge of Linux is
> shaky: I understand that this is to do with permissions, so I defer to
> you as how to deal with this. (Would it be a "chmod" ? Is that the one
> ?)
>
> I have to say it puzzles me slightly in that logged in to Suse, I have
> no problem reading from or writing to the FREECOM device.
>
> Hope that helps.
>
> Thanks :-)
>
> Reler
>
> You received this question notification because you are an answer
> contact for Back In Time.
>

Hi Bart - did you mean "ls -als /home/reler/BBR/bit_test" instead of "ls -als /home/reler/BBR" ? The first is the path specified to BIT in the settings. /home/reler/BBR has about 50 files in it and I am guessing that you don't want to see all of that on here.

But if that is what you meant, there is of course an entry for the bit_test directory and that looks like this under OpenSuse 11.0:
   4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 bit_test
and like this under Ubuntu:
   4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 bit_test

But assuming you meant ls -als /home/reler/BBR/bit_test, here is the output ...

OpenSuse 11.0
=============
reler@linux-tx7g:~> ls -als /home/reler/BBR/bit_test
total 16
4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 .
4 drwxr-xr-x 8 reler users 4096 2009-11-17 23:45 ..
8 -rw-r--r-- 1 reler users 10 2009-11-21 11:40 test.txt
0 -rw-r--r-- 1 reler users 0 2009-11-21 11:40 test.txt~
reler@linux-tx7g:~>

I wasn't certain if you wanted the same from Ubuntu, because obviously the path needs to be specified slightly differently. Here it is anyway:

Ubuntu 9.04
===========
reler@reler-desktop:~$ ls -als /media/dev_sda9/reler-nbs/BBR/bit_test
total 16
4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 .
4 drwxr-xr-x 8 reler users 4096 2009-11-17 23:45 ..
8 -rw-r--r-- 1 reler users 10 2009-11-21 11:40 test.txt
0 -rw-r--r-- 1 reler users 0 2009-11-21 11:40 test.txt~
reler@reler-desktop:~$

In other words, it seems to be the same. I'm not sure what this means ?

Regards,

Reler

Hmmm, could you try the following as root:
(I guess that the GID of users = 1000, otherwise change that to the correct
number)
first umount:
umount /dev/sdc1
then remount:
mount -o rw,nosuid,nodev,uhelper=hal,
shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush
/dev/sdc1 "/media/FREECOM HDD"

2009/12/3 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> Status: Answered => Open
>
> reler is still having a problem:
> Hi Bart - did you mean "ls -als /home/reler/BBR/bit_test" instead of "ls
> -als /home/reler/BBR" ? The first is the path specified to BIT in the
> settings. /home/reler/BBR has about 50 files in it and I am guessing
> that you don't want to see all of that on here.
>
> But if that is what you meant, there is of course an entry for the bit_test
> directory and that looks like this under OpenSuse 11.0:
> 4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 bit_test
> and like this under Ubuntu:
> 4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 bit_test
>
> But assuming you meant ls -als /home/reler/BBR/bit_test, here is the
> output ...
>
> OpenSuse 11.0
> =============
> reler@linux-tx7g:~> ls -als /home/reler/BBR/bit_test
> total 16
> 4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 .
> 4 drwxr-xr-x 8 reler users 4096 2009-11-17 23:45 ..
> 8 -rw-r--r-- 1 reler users 10 2009-11-21 11:40 test.txt
> 0 -rw-r--r-- 1 reler users 0 2009-11-21 11:40 test.txt~
> reler@linux-tx7g:~>
>
> I wasn't certain if you wanted the same from Ubuntu, because obviously
> the path needs to be specified slightly differently. Here it is anyway:
>
> Ubuntu 9.04
> ===========
> reler@reler-desktop:~$ ls -als /media/dev_sda9/reler-nbs/BBR/bit_test
> total 16
> 4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 .
> 4 drwxr-xr-x 8 reler users 4096 2009-11-17 23:45 ..
> 8 -rw-r--r-- 1 reler users 10 2009-11-21 11:40 test.txt
> 0 -rw-r--r-- 1 reler users 0 2009-11-21 11:40 test.txt~
> reler@reler-desktop:~$
>
> In other words, it seems to be the same. I'm not sure what this means ?
>
> Regards,
>
> Reler
>
> You received this question notification because you are an answer
> contact for Back In Time.
>

Sorry that should be done as one command:

mount -o
rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush
/dev/sdc1 "/media/FREECOM HDD"

Good luck!
Bart

2009/12/3 Bart <email address hidden>

>
> Hmmm, could you try the following as root:
> (I guess that the GID of users = 1000, otherwise change that to the correct
> number)
> first umount:
> umount /dev/sdc1
> then remount:
> mount -o rw,nosuid,nodev,uhelper=hal,
> shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush
> /dev/sdc1 "/media/FREECOM HDD"
>
>
> 2009/12/3 reler <email address hidden>
>
>> Question #90701 on Back In Time changed:
>>
>> https://answers.launchpad.net/backintime/+question/90701
>>
>> Status: Answered => Open
>>
>> reler is still having a problem:
>> Hi Bart - did you mean "ls -als /home/reler/BBR/bit_test" instead of "ls
>> -als /home/reler/BBR" ? The first is the path specified to BIT in the
>> settings. /home/reler/BBR has about 50 files in it and I am guessing
>> that you don't want to see all of that on here.
>>
>> But if that is what you meant, there is of course an entry for the
>> bit_test directory and that looks like this under OpenSuse 11.0:
>> 4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 bit_test
>> and like this under Ubuntu:
>> 4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 bit_test
>>
>> But assuming you meant ls -als /home/reler/BBR/bit_test, here is the
>> output ...
>>
>> OpenSuse 11.0
>> =============
>> reler@linux-tx7g:~> ls -als /home/reler/BBR/bit_test
>> total 16
>> 4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 .
>> 4 drwxr-xr-x 8 reler users 4096 2009-11-17 23:45 ..
>> 8 -rw-r--r-- 1 reler users 10 2009-11-21 11:40 test.txt
>> 0 -rw-r--r-- 1 reler users 0 2009-11-21 11:40 test.txt~
>> reler@linux-tx7g:~>
>>
>> I wasn't certain if you wanted the same from Ubuntu, because obviously
>> the path needs to be specified slightly differently. Here it is anyway:
>>
>> Ubuntu 9.04
>> ===========
>> reler@reler-desktop:~$ ls -als /media/dev_sda9/reler-nbs/BBR/bit_test
>> total 16
>> 4 drwxr-xr-x 2 reler users 4096 2009-11-21 11:40 .
>> 4 drwxr-xr-x 8 reler users 4096 2009-11-17 23:45 ..
>> 8 -rw-r--r-- 1 reler users 10 2009-11-21 11:40 test.txt
>> 0 -rw-r--r-- 1 reler users 0 2009-11-21 11:40 test.txt~
>> reler@reler-desktop:~$
>>
>> In other words, it seems to be the same. I'm not sure what this means ?
>>
>> Regards,
>>
>> Reler
>>
>> You received this question notification because you are an answer
>> contact for Back In Time.
>>
>
>

Hi Bart - first, I have no idea about the GID parameter. Sorry - usual excuse: Linux newb, Windoze refugee. This probably also accounts for my lack of success with the second part of your instructions.

BTW, on the SuSe system, the drive is /dev/sdb1, on Ubuntu, it's /dev/sdc1, so I substituted the first of these in your instructions. This is what happens:
   reler@linux-tx7g:~> gnomesu umount /dev/sdb1

Now check whether device is loaded with ...
   reler@linux-tx7g:~> mount
Device now no longer listed - good.

Now the mount command. Even though you tried to respecify this, the launchpad format means that lines are wrapped, so I am unsure if I have this right. I copied the text from your last post in to gedit and it spanned 3 lines: there was a break after "-o", also after "flush", so I have put spaces in their place to get this command, which has no CR/LF in it (even if it does wrap around again here !) ...

   gnomesu mount -o rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush /dev/sdb1 "/media/FREECOM HDD"

This just gives me a load of verbiage about usage:
-------------------------------
reler@linux-tx7g:~> gnomesu mount -o rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush /dev/sdb1 "/media/FREECOM HDD"
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
reler@linux-tx7g:~>
-------------------------------

I have to go somewhere now otherwise I would play with this to see if I can work it out, so I am just reporting this in case it's an easy answer ! Otherwise I'll pick this up later ;-)

Thanks,

Reler

If you use gnomesu please put the whole command between "" (So a double "
after HDD)
With Suse it think it is better to use su directly or install sudo if you
want to work directly from the commandline. In both cases you do not have to
add the "". Gnomesu is intended for graphical use.

Cheers,
Bart

2009/12/3 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> Status: Answered => Open
>
> reler is still having a problem:
> Hi Bart - first, I have no idea about the GID parameter. Sorry - usual
> excuse: Linux newb, Windoze refugee. This probably also accounts for my
> lack of success with the second part of your instructions.
>
> BTW, on the SuSe system, the drive is /dev/sdb1, on Ubuntu, it's /dev/sdc1,
> so I substituted the first of these in your instructions. This is what
> happens:
> reler@linux-tx7g:~> gnomesu umount /dev/sdb1
>
> Now check whether device is loaded with ...
> reler@linux-tx7g:~> mount
> Device now no longer listed - good.
>
> Now the mount command. Even though you tried to respecify this, the
> launchpad format means that lines are wrapped, so I am unsure if I have
> this right. I copied the text from your last post in to gedit and it
> spanned 3 lines: there was a break after "-o", also after "flush", so I
> have put spaces in their place to get this command, which has no CR/LF
> in it (even if it does wrap around again here !) ...
>
> gnomesu mount -o
>
> rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush
> /dev/sdb1 "/media/FREECOM HDD"
>
> This just gives me a load of verbiage about usage:
> -------------------------------
> reler@linux-tx7g:~> gnomesu mount -o
> rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush
> /dev/sdb1 "/media/FREECOM HDD"
> Usage: mount -V : print version
> mount -h : print this help
> mount : list mounted filesystems
> mount -l : idem, including volume labels
> So far the informational part. Next the mounting.
> The command is `mount [-t fstype] something somewhere'.
> Details found in /etc/fstab may be omitted.
> mount -a [-t|-O] ... : mount all stuff from /etc/fstab
> mount device : mount device at the known place
> mount directory : mount known device here
> mount -t type dev dir : ordinary mount command
> Note that one does not really mount a device, one mounts
> a filesystem (of the given type) found on the device.
> One can also mount an already visible directory tree elsewhere:
> mount --bind olddir newdir
> or move a subtree:
> mount --move olddir newdir
> One can change the type of mount containing the directory dir:
> mount --make-shared dir
> mount --make-slave dir
> mount --make-private dir
> mount --make-unbindable dir
> One can change the type of all the mounts in a mount subtree
> containing the directory dir:
> mount --make-rshared dir
> mount --make-rslave dir
> mount --make-rprivate dir
> mount --make-runbindable dir
> A device can be given by name, say /dev/hda1 or /dev/cdrom,
> or by label, using -L label or by uuid, using -U uuid .
> Other options: [-nfFrsvw] [-o options] [-p passwdfd].
> For many more details, say man 8 mount .
> reler@linux-tx7g:~>
> -------------------------------
>
> I have to go somewhere now otherwise I would play with this to see if I
> can work it out, so I am just reporting this in case it's an easy answer
> ! Otherwise I'll pick this up later ;-)
>
> Thanks,
>
> Reler
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

OK, I'm back. Thanks for putting me straight on gnomesu/su/sudo, etc.

  sudo umount /dev/sdb1
was fine and mount on its own did not list the device. Then ...

reler@linux-tx7g:~> sudo mount -o rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush /dev/sdb1 "/media/FREECOM HDD"
mount: mount point /media/FREECOM HDD does not exist

Tried this:
reler@linux-tx7g:~> su root "mount -o rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush /dev/sdb1 "/media/FREECOM HDD""
Password:
bash: mount -o rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush /dev/sdb1 /media/FREECOM: No such file or directory

Sorry ! Is the space in "FREECOM HDD" a problem ?

Reler

No sorry, mount cannot attach devices to non-existing points, my fault...
Try:
sudo mkdir "/media/FREECOM HDD"
and try the command again
If you succeed try to run backintime -b from the command line and forward
the output

To undo this afterwards umount /dev/sdb1 (sorry for the mistake by the way)
and sudo rmdir "/media/FREECOM HDD"

Good luck!

Cheers,
Bart

2009/12/3 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> Status: Answered => Open
>
> reler is still having a problem:
> OK, I'm back. Thanks for putting me straight on gnomesu/su/sudo, etc.
>
> sudo umount /dev/sdb1
> was fine and mount on its own did not list the device. Then ...
>
> reler@linux-tx7g:~> sudo mount -o
> rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush
> /dev/sdb1 "/media/FREECOM HDD"
> mount: mount point /media/FREECOM HDD does not exist
>
> Tried this:
> reler@linux-tx7g:~> su root "mount -o
> rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush
> /dev/sdb1 "/media/FREECOM HDD""
> Password:
> bash: mount -o
> rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,gid=1000,utf8,umask=077,flush
> /dev/sdb1 /media/FREECOM: No such file or directory
>
> Sorry ! Is the space in "FREECOM HDD" a problem ?
>
> Reler
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

Hi Bart - OK, your mount suggestions worked, thanks. I then ran "backintime -b" as suggested and got this:
------------------------------------
reler@linux-tx7g:~> backintime -b
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

INFO: Lock
INFO: Include folders: ['/home/reler/BBR/bit_test']
INFO: Ignore folders: []
INFO: Last snapshots: {}
INFO: [GnomePlugin.Systray.run]
INFO: [GnomePlugin.Systray.run] begin loop
INFO: Compare with old snapshot: 20091203-150829
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/share/backintime/plugins/gnomeplugin.py", line 111, in run
    self.notification.attach_to_status_icon( status_icon )
AttributeError: 'pynotify.Notification' object has no attribute 'attach_to_status_icon'

INFO: Command "rsync -aEAX -i --dry-run --chmod=Fa-w,D+w --whole-file --delete --exclude="/media/FREECOM HDD" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/media/FREECOM HDD/backintime/20091203-150829/backup/"" returns 0
INFO: Create hard-links
INFO: Command "cp -al "/media/FREECOM HDD/backintime/20091203-150829/backup/"* "/media/FREECOM HDD/backintime/new_snapshot/backup/"" returns 0
INFO: Call rsync to take the snapshot
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler" failed: Operation not permitted (1)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR" failed: Operation not permitted (1)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test" failed: Operation not permitted (1)
rsync: rsync_xal_set: lsetxattr("home/reler","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler" failed: Operation not permitted (1)
rsync: rsync_xal_set: lsetxattr("home/reler/BBR","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR" failed: Operation not permitted (1)
rsync: rsync_xal_set: lsetxattr("home/reler/BBR/bit_test","user.Beagle") failed: Operation not supported (95)
rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test" failed: Operation not permitted (1)
rsync: mkstemp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test/.test.txt.UtOL0l" failed: Operation not permitted (1)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]
WARNING: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/media/FREECOM HDD" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/media/FREECOM HDD/backintime/new_snapshot/backup/"" returns 5888
INFO: Save permissions
INFO: Remove backups older than: 19991204-000000
INFO: Keep min free disk space: 1024 Mb
INFO: Unlock
reler@linux-tx7g:~>
------------------------------------

At first glance, we seem to still have the attach_to_status_icon problem that Dan and I discussed at length.

(Whilst on that subject, please see my previous comments about the "src/pynotify.c does not get rebuilt properly" threads that I posted. I am focussed on them because they seem to relate to the attach_to_status_icon stuff. I just wanted to clarify to you guys, that I am not necessarily expecting you to provide me with a package for my Suse system. I understand that you don't do that. But I AM willing to indulge in a little judicious recompilation for myself, particularly if pointed in the right direction. AND particularly because these questions seem directly related to this problem.)

Or is it the permissions ?

Over to you ... thanks again for your help,

Reler

Well you have quite a difficult problem to understand from a distance. I
personally think it is permissions, however Dan expect the pynotify to be
the problem. Because quite some people use BiT on SuSe systems, I expect
that this could not be the problem...
What you could try first is to change the backup folder to a local place, so
not on your external drive, but on the local harddisk, within your home
folder.
That should work if it was a permission related problem.
Cheers,
Bart

2009/12/4 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> Status: Answered => Open
>
> reler is still having a problem:
> Hi Bart - OK, your mount suggestions worked, thanks. I then ran "backintime
> -b" as suggested and got this:
> ------------------------------------
> reler@linux-tx7g:~> backintime -b
> Back In Time
> Version: 0.9.26
>

>
> Back In Time comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `backintime --license' for details.
>
> INFO: Lock
> INFO: Include folders: ['/home/reler/BBR/bit_test']
> INFO: Ignore folders: []
> INFO: Last snapshots: {}
> INFO: [GnomePlugin.Systray.run]
> INFO: [GnomePlugin.Systray.run] begin loop
> INFO: Compare with old snapshot: 20091203-150829
> Exception in thread Thread-1:
> Traceback (most recent call last):
> File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
> self.run()
> File "/usr/share/backintime/plugins/gnomeplugin.py", line 111, in run
> self.notification.attach_to_status_icon( status_icon )
> AttributeError: 'pynotify.Notification' object has no attribute
> 'attach_to_status_icon'
>
> INFO: Command "rsync -aEAX -i --dry-run --chmod=Fa-w,D+w --whole-file
> --delete --exclude="/media/FREECOM HDD"
> --exclude="/home/reler/.local/share/backintime"
> --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/"
> --include="/home/reler/" --include="/home/" --exclude=".*"
> --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**"
> --exclude="*" / "/media/FREECOM HDD/backintime/20091203-150829/backup/""
> returns 0
> INFO: Create hard-links
> INFO: Command "cp -al "/media/FREECOM
> HDD/backintime/20091203-150829/backup/"* "/media/FREECOM
> HDD/backintime/new_snapshot/backup/"" returns 0
> INFO: Call rsync to take the snapshot
> rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler"
> failed: Operation not permitted (1)
> rsync: chgrp "/media/FREECOM
> HDD/backintime/new_snapshot/backup/home/reler/BBR" failed: Operation not
> permitted (1)
> rsync: chgrp "/media/FREECOM
> HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test" failed:
> Operation not permitted (1)
> rsync: rsync_xal_set: lsetxattr("home/reler","user.Beagle") failed:
> Operation not supported (95)
> rsync: chgrp "/media/FREECOM HDD/backintime/new_snapshot/backup/home/reler"
> failed: Operation not permitted (1)
> rsync: rsync_xal_set: lsetxattr("home/reler/BBR","user.Beagle") failed:
> Operation not supported (95)
> rsync: chgrp "/media/FREECOM
> HDD/backintime/new_snapshot/backup/home/reler/BBR" failed: Operation not
> permitted (1)
> rsync: rsync_xal_set: lsetxattr("home/reler/BBR/bit_test","user.Beagle")
> failed: Operation not supported (95)
> rsync: chgrp "/media/FREECOM
> HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test" failed:
> Operation not permitted (1)
> rsync: mkstemp "/media/FREECOM
> HDD/backintime/new_snapshot/backup/home/reler/BBR/bit_test/.test.txt.UtOL0l"
> failed: Operation not permitted (1)
> rsync error: some files/attrs were not transferred (see previous errors)
> (code 23) at main.c(1039) [sender=3.0.6]
> WARNING: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w
> --whole-file --delete --exclude="/media/FREECOM HDD"
> --exclude="/home/reler/.local/share/backintime"
> --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/"
> --include="/home/reler/" --include="/home/" --exclude=".*"
> --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**"
> --exclude="*" / "/media/FREECOM HDD/backintime/new_snapshot/backup/""
> returns 5888
> INFO: Save permissions
> INFO: Remove backups older than: 19991204-000000
> INFO: Keep min free disk space: 1024 Mb
> INFO: Unlock
> reler@linux-tx7g:~>
> ------------------------------------
>
> At first glance, we seem to still have the attach_to_status_icon problem
> that Dan and I discussed at length.
>
> (Whilst on that subject, please see my previous comments about the
> "src/pynotify.c does not get rebuilt properly" threads that I posted. I
> am focussed on them because they seem to relate to the
> attach_to_status_icon stuff. I just wanted to clarify to you guys, that
> I am not necessarily expecting you to provide me with a package for my
> Suse system. I understand that you don't do that. But I AM willing to
> indulge in a little judicious recompilation for myself, particularly if
> pointed in the right direction. AND particularly because these questions
> seem directly related to this problem.)
>
> Or is it the permissions ?
>
> Over to you ... thanks again for your help,
>
> Reler
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

Hi Bart - putting the backup elsewhere is so obvious a thing to do, I am kicking myself that I didn't think of it ! Sorry. When I do, it seems to work, so I think that you are right, it must be to do with the permissions.

But there are lots of message s issues and I will post tomorrow with many more details.

Thanks,

Reler

OK, in addition to what I did late last night. today I took another trial backup, just to make sure that was working. It was.

Then, I added a new file to the source directory and took another new backup to a target which is NOT on the external drive. Here is the output from that:
------------------------------
reler@linux-tx7g:~> backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

INFO: Lock
INFO: Include folders: ['/home/reler/BBR/bit_test']
INFO: Ignore folders: []
INFO: Last snapshots: {}
INFO: [GnomePlugin.Systray.run]
INFO: [GnomePlugin.Systray.run] begin loop
INFO: Compare with old snapshot: 20091206-010836
INFO: Command "rsync -aEAX -i --dry-run --chmod=Fa-w,D+w --whole-file --delete --exclude="/home/reler/bittest2" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/home/reler/bittest2/backintime/20091206-010836/backup/"" returns 0
INFO: Create hard-links
INFO: Command "cp -al "/home/reler/bittest2/backintime/20091206-010836/backup/"* "/home/reler/bittest2/backintime/new_snapshot/backup/"" returns 0
INFO: Call rsync to take the snapshot
rsync: rsync_xal_set: lsetxattr("home/reler/BBR/bit_test/test.txt","user.Beagle") failed: Permission denied (13)
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/share/backintime/plugins/gnomeplugin.py", line 111, in run
    self.notification.attach_to_status_icon( status_icon )
AttributeError: 'pynotify.Notification' object has no attribute 'attach_to_status_icon'

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]
WARNING: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/home/reler/bittest2" --exclude="/home/reler/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude=".*" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/home/reler/bittest2/backintime/new_snapshot/backup/"" returns 5888
INFO: Save permissions
INFO: Remove backups older than: 19991206-000000
INFO: Keep min free disk space: 1024 Mb
INFO: Unlock
reler@linux-tx7g:~>
------------------------------

Then, I deleted the new file in the source directory and re-ran to do teh recovery. This is the output:
------------------------------
reler@linux-tx7g:~> backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

INFO: Restore: /home/reler/BBR/bit_test/test2.txt
sending incremental file list
home/
rsync: chgrp "/home" failed: Operation not permitted (1)
home/reler/BBR/bit_test/test2.txt

sent 313 bytes received 38 bytes 702.00 bytes/sec
total size is 10 speedup is 0.03
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]
WARNING: Command "rsync -avRAXE --whole-file --backup --suffix=.backup.20091206 --chmod=+w "/home/reler/bittest2/backintime/20091206-121532/backup/./home/reler/BBR/bit_test/test2.txt" /" returns 5888
reler@linux-tx7g:~>
------------------------------

So it seems to me that there is still some attach_to_status_icon stuff going on but that it's not the main thing. But I'd guess that there are still some permission problems.

Any further ideas ?

Thanks,

Reler

Could you try to run BiT as root, again on the internal drive? If you see
the same error again, the error is related to the ACL implementation (you
have the newest rsync haven't you?), if not we are dealing with a permission
problem...

Cheers,
Bart

2009/12/6 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> reler gave more information on the question:
> OK, in addition to what I did late last night. today I took another
> trial backup, just to make sure that was working. It was.
>
> Then, I added a new file to the source directory and took another new
> backup to a target which is NOT on the external drive. Here is the output
> from that:
> ------------------------------
> reler@linux-tx7g:~> backintime-gnome
> Back In Time
> Version: 0.9.26
>
> Back In Time comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `backintime-gnome --license' for details.
>
> Back In Time
> Version: 0.9.26
>
> Back In Time comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `backintime --license' for details.
>
> INFO: Lock
> INFO: Include folders: ['/home/reler/BBR/bit_test']
> INFO: Ignore folders: []
> INFO: Last snapshots: {}
> INFO: [GnomePlugin.Systray.run]
> INFO: [GnomePlugin.Systray.run] begin loop
> INFO: Compare with old snapshot: 20091206-010836
> INFO: Command "rsync -aEAX -i --dry-run --chmod=Fa-w,D+w --whole-file
> --delete --exclude="/home/reler/bittest2"
> --exclude="/home/reler/.local/share/backintime"
> --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/"
> --include="/home/reler/" --include="/home/" --exclude=".*"
> --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**"
> --exclude="*" / "/home/reler/bittest2/backintime/20091206-010836/backup/""
> returns 0
> INFO: Create hard-links
> INFO: Command "cp -al
> "/home/reler/bittest2/backintime/20091206-010836/backup/"*
> "/home/reler/bittest2/backintime/new_snapshot/backup/"" returns 0
> INFO: Call rsync to take the snapshot
> rsync: rsync_xal_set:
> lsetxattr("home/reler/BBR/bit_test/test.txt","user.Beagle") failed:
> Permission denied (13)
> Exception in thread Thread-1:
> Traceback (most recent call last):
> File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
> self.run()
> File "/usr/share/backintime/plugins/gnomeplugin.py", line 111, in run
> self.notification.attach_to_status_icon( status_icon )
> AttributeError: 'pynotify.Notification' object has no attribute
> 'attach_to_status_icon'
>
> rsync error: some files/attrs were not transferred (see previous errors)
> (code 23) at main.c(1039) [sender=3.0.6]
> WARNING: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w
> --whole-file --delete --exclude="/home/reler/bittest2"
> --exclude="/home/reler/.local/share/backintime"
> --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/"
> --include="/home/reler/" --include="/home/" --exclude=".*"
> --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**"
> --exclude="*" / "/home/reler/bittest2/backintime/new_snapshot/backup/""
> returns 5888
> INFO: Save permissions
> INFO: Remove backups older than: 19991206-000000
> INFO: Keep min free disk space: 1024 Mb
> INFO: Unlock
> reler@linux-tx7g:~>
> ------------------------------
>
> Then, I deleted the new file in the source directory and re-ran to do teh
> recovery. This is the output:
> ------------------------------
> reler@linux-tx7g:~> backintime-gnome
> Back In Time
> Version: 0.9.26
>
> Back In Time comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `backintime-gnome --license' for details.
>
> INFO: Restore: /home/reler/BBR/bit_test/test2.txt
> sending incremental file list
> home/
> rsync: chgrp "/home" failed: Operation not permitted (1)
> home/reler/BBR/bit_test/test2.txt
>
> sent 313 bytes received 38 bytes 702.00 bytes/sec
> total size is 10 speedup is 0.03
> rsync error: some files/attrs were not transferred (see previous errors)
> (code 23) at main.c(1039) [sender=3.0.6]
> WARNING: Command "rsync -avRAXE --whole-file --backup
> --suffix=.backup.20091206 --chmod=+w
> "/home/reler/bittest2/backintime/20091206-121532/backup/./home/reler/BBR/bit_test/test2.txt"
> /" returns 5888
> reler@linux-tx7g:~>
> ------------------------------
>
> So it seems to me that there is still some attach_to_status_icon stuff
> going on but that it's not the main thing. But I'd guess that there are
> still some permission problems.
>
> Any further ideas ?
>
> Thanks,
>
> Reler
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

OK Bart, bBefore anything else, here's the rsync info again ...

reler@linux-tx7g:~> rsync --version
rsync version 3.0.6 protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, symtimes

I believe that this makes it the latest version. This is what I then did following your last post ...
----------------------------
1.
reler@linux-tx7g:~> sudo backintime-gnome ...
... followed by change to back up directory to an internal drive. Exit.
----------------------------
2. Call again to create a new backup ...
reler@linux-tx7g:~> sudo backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

/usr/share/backintime/gnome/settingsdialog.py:296: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  if gtk.RESPONSE_OK == self.dialog.run():
/usr/share/backintime/gnome/settingsdialog.py:300: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  self.dialog.destroy()
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

INFO: Lock
INFO: Include folders: ['/home/reler/BBR/bit_test']
INFO: Ignore folders: []
INFO: Last snapshots: {}
INFO: [GnomePlugin.Systray.run]
INFO: [GnomePlugin.Systray.run] begin loop
INFO: Call rsync to take the snapshot
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/share/backintime/plugins/gnomeplugin.py", line 111, in run
    self.notification.attach_to_status_icon( status_icon )
AttributeError: 'pynotify.Notification' object has no attribute 'attach_to_status_icon'

INFO: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/root" --exclude="/root/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/root/backintime/new_snapshot/backup/"" returns 0
INFO: Save permissions
INFO: Remove backups older than: 19991207-000000
INFO: Keep min free disk space: 1024 Mb
INFO: Unlock
reler@linux-tx7g:~>

In spite of error messages shown, all seems well. Exit to delete a test file from backed-up location.
----------------------------
3. Delete file test2.txt
----------------------------
4. Call again to do a restore ...

reler@linux-tx7g:~> sudo backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

INFO: Restore: /home/reler/BBR/bit_test/test2.txt
sending incremental file list
home/reler/BBR/bit_test/test2.txt

sent 312 bytes received 35 bytes 694.00 bytes/sec
total size is 10 speedup is 0.03
INFO: Command "rsync -avRAXE --whole-file --backup --suffix=.backup.20091207 --chmod=+w "/root/backintime/20091207-141831/backup/./home/reler/BBR/bit_test/test2.txt" /" returns 0
reler@linux-tx7g:~>

Again, despite one or two error messages, the restore appears to work fine.
----------------------------

What do you reckon ?

Reler

What I thought already it is a permission related problem...
Could you make a snapshot also to your external hdd as root?

2009/12/7 reler <email address hidden>

> Question #90701 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/90701
>
> Status: Answered => Open
>
> reler is still having a problem:
> OK Bart, bBefore anything else, here's the rsync info again ...
>
> reler@linux-tx7g:~> rsync --version
> rsync version 3.0.6 protocol version 30
> Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
> Web site: http://rsync.samba.org/
> Capabilities:
> 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
> socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
> append, ACLs, xattrs, iconv, symtimes
>
> I believe that this makes it the latest version. This is what I then did
> following your last post ...
> ----------------------------
> 1.
> reler@linux-tx7g:~> sudo backintime-gnome ...
> ... followed by change to back up directory to an internal drive. Exit.
> ----------------------------
> 2. Call again to create a new backup ...
> reler@linux-tx7g:~> sudo backintime-gnome
> Back In Time
> Version: 0.9.26
>
> Back In Time comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `backintime-gnome --license' for details.
>
> /usr/share/backintime/gnome/settingsdialog.py:296: Warning: g_object_unref:
> assertion `G_IS_OBJECT (object)' failed
> if gtk.RESPONSE_OK == self.dialog.run():
> /usr/share/backintime/gnome/settingsdialog.py:300: Warning: g_object_unref:
> assertion `G_IS_OBJECT (object)' failed
> self.dialog.destroy()
> Back In Time
> Version: 0.9.26
>
> Back In Time comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `backintime --license' for details.
>
> INFO: Lock
> INFO: Include folders: ['/home/reler/BBR/bit_test']
> INFO: Ignore folders: []
> INFO: Last snapshots: {}
> INFO: [GnomePlugin.Systray.run]
> INFO: [GnomePlugin.Systray.run] begin loop
> INFO: Call rsync to take the snapshot
> Exception in thread Thread-1:
> Traceback (most recent call last):
> File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
> self.run()
> File "/usr/share/backintime/plugins/gnomeplugin.py", line 111, in run
> self.notification.attach_to_status_icon( status_icon )
> AttributeError: 'pynotify.Notification' object has no attribute
> 'attach_to_status_icon'
>
> INFO: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w
> --whole-file --delete --exclude="/root"
> --exclude="/root/.local/share/backintime"
> --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/"
> --include="/home/reler/" --include="/home/" --exclude="*.backup*"
> --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" /
> "/root/backintime/new_snapshot/backup/"" returns 0
> INFO: Save permissions
> INFO: Remove backups older than: 19991207-000000
> INFO: Keep min free disk space: 1024 Mb
> INFO: Unlock
> reler@linux-tx7g:~>
>
> In spite of error messages shown, all seems well. Exit to delete a test
> file from backed-up location.
> ----------------------------
> 3. Delete file test2.txt
> ----------------------------
> 4. Call again to do a restore ...
>
> reler@linux-tx7g:~> sudo backintime-gnome
> Back In Time
> Version: 0.9.26
>
> Back In Time comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `backintime-gnome --license' for details.
>
> INFO: Restore: /home/reler/BBR/bit_test/test2.txt
> sending incremental file list
> home/reler/BBR/bit_test/test2.txt
>
> sent 312 bytes received 35 bytes 694.00 bytes/sec
> total size is 10 speedup is 0.03
> INFO: Command "rsync -avRAXE --whole-file --backup
> --suffix=.backup.20091207 --chmod=+w
> "/root/backintime/20091207-141831/backup/./home/reler/BBR/bit_test/test2.txt"
> /" returns 0
> reler@linux-tx7g:~>
>
> Again, despite one or two error messages, the restore appears to work fine.
> ----------------------------
>
> What do you reckon ?
>
> Reler
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

OK - I thought that I had tried this before raising this ticket, but I must have done something differently. I am not quite sure what went on here but here goes ...

First, I tried this:
-------------------------
reler@linux-tx7g:~> sudo backintime-gnome
Invalid MIT-MAGIC-COOKIE-1 key/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

/usr/share/backintime/gnome/app.py:105: Warning: invalid (NULL) pointer instance
  self.glade = gtk.glade.XML( os.path.join( self.config.get_app_path(), 'gnome', 'mainwindow.glade' ), None, 'backintime' )
/usr/share/backintime/gnome/app.py:105: Warning: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
  self.glade = gtk.glade.XML( os.path.join( self.config.get_app_path(), 'gnome', 'mainwindow.glade' ), None, 'backintime' )
/usr/share/backintime/gnome/app.py:105: GtkWarning: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  self.glade = gtk.glade.XML( os.path.join( self.config.get_app_path(), 'gnome', 'mainwindow.glade' ), None, 'backintime' )
/usr/share/backintime/gnome/fileicons.py:27: GtkWarning: gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  self.all_icons = gtk.icon_theme_get_default().list_icons()
Traceback (most recent call last):
  File "/usr/share/backintime/gnome/app.py", line 1056, in <module>
    main_window = MainWindow( cfg, app_instance )
  File "/usr/share/backintime/gnome/app.py", line 139, in __init__
    self.icon_names = fileicons.GnomeFileIcons()
  File "/usr/share/backintime/gnome/fileicons.py", line 27, in __init__
    self.all_icons = gtk.icon_theme_get_default().list_icons()
AttributeError: 'NoneType' object has no attribute 'list_icons'
reler@linux-tx7g:~>
----------------------------------------
FIgured I'd need gnomesu for this !

reler@linux-tx7g:~> gnomesu backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

/usr/share/backintime/gnome/settingsdialog.py:296: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  if gtk.RESPONSE_OK == self.dialog.run():
/usr/share/backintime/gnome/settingsdialog.py:379: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  snapshots_path = self.fcb_where.get_filename()
Snapshots path: /root
Automatic backup: Disabled
/usr/share/backintime/gnome/settingsdialog.py:300: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  self.dialog.destroy()
INFO: Restore: /home/reler/BBR/bit_test/test2.txt
sending incremental file list
home/reler/BBR/bit_test/test2.txt

sent 312 bytes received 35 bytes 694.00 bytes/sec
total size is 10 speedup is 0.03
INFO: Command "rsync -avRAXE --whole-file --backup --suffix=.backup.20091208 --chmod=+w "/root/backintime/20091207-141831/backup/./home/reler/BBR/bit_test/test2.txt" /" returns 0
reler@linux-tx7g:~>
-----------------------------------------
Then ended session & deleted files from test directory.
Now restart in the same way to see if we can restore.
-----------------------------------------
reler@linux-tx7g:~> gnomesu backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

Remove Snapshot: 20091207-141831
INFO: Command "chmod -R a+rwx "/root/backintime/20091207-141831"" returns 0
removed `/root/backintime/20091207-141831/fileinfo.bz2'
removed `/root/backintime/20091207-141831/backup/home/reler/BBR/bit_test/test.txt'
removed `/root/backintime/20091207-141831/backup/home/reler/BBR/bit_test/test2.txt'
removed directory: `/root/backintime/20091207-141831/backup/home/reler/BBR/bit_test'
removed directory: `/root/backintime/20091207-141831/backup/home/reler/BBR'
removed directory: `/root/backintime/20091207-141831/backup/home/reler'
removed directory: `/root/backintime/20091207-141831/backup/home'
removed directory: `/root/backintime/20091207-141831/backup'
removed `/root/backintime/20091207-141831/info'
removed directory: `/root/backintime/20091207-141831'
INFO: Command "rm -rfv "/root/backintime/20091207-141831"" returns 0
/usr/share/backintime/gnome/settingsdialog.py:296: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  if gtk.RESPONSE_OK == self.dialog.run():
/usr/share/backintime/gnome/settingsdialog.py:379: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  snapshots_path = self.fcb_where.get_filename()
Snapshots path: /root
Automatic backup: Disabled
/usr/share/backintime/gnome/settingsdialog.py:300: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  self.dialog.destroy()
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

INFO: Lock
INFO: Include folders: ['/home/reler/BBR/bit_test']
INFO: Ignore folders: []
INFO: Last snapshots: {}
INFO: [GnomePlugin.Systray.run]
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
INFO: [GnomePlugin.Systray.run] begin loop
INFO: Call rsync to take the snapshot
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/share/backintime/plugins/gnomeplugin.py", line 111, in run
    self.notification.attach_to_status_icon( status_icon )
AttributeError: 'pynotify.Notification' object has no attribute 'attach_to_status_icon'

INFO: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/root" --exclude="/root/.local/share/backintime" --include="/home/reler/BBR/bit_test/" --include="/home/reler/BBR/" --include="/home/reler/" --include="/home/" --exclude="*.backup*" --exclude="*~" --include="/home/reler/BBR/bit_test/**" --exclude="*" / "/root/backintime/new_snapshot/backup/"" returns 0
INFO: Save permissions
INFO: Remove backups older than: 19991208-000000
INFO: Keep min free disk space: 1024 Mb
INFO: Unlock
reler@linux-tx7g:~> gnomesu backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

INFO: Restore: /home/reler/BBR/bit_test/test.txt
sending incremental file list
home/reler/BBR/bit_test/test.txt

sent 453 bytes received 37 bytes 980.00 bytes/sec
total size is 10 speedup is 0.02
INFO: Command "rsync -avRAXE --whole-file --backup --suffix=.backup.20091208 --chmod=+w "/root/backintime/20091208-092054/backup/./home/reler/BBR/bit_test/test.txt" /" returns 0
INFO: Restore: /home/reler/BBR/bit_test/test2.txt
sending incremental file list
home/reler/BBR/bit_test/test2.txt

sent 312 bytes received 35 bytes 694.00 bytes/sec
total size is 10 speedup is 0.03
INFO: Command "rsync -avRAXE --whole-file --backup --suffix=.backup.20091208 --chmod=+w "/root/backintime/20091208-092054/backup/./home/reler/BBR/bit_test/test2.txt" /" returns 0
reler@linux-tx7g:~>
-------------------------------------------
So in spite of all the messages, it seems to work !

So that's good, though I am not sure if this means that I can run it under cron. Can you run root under cron ? Sounds dangerous ...

Reler

If a user "A" has crontab entries, then cron will run them as "A"'.
'root' user like other users can have it's crontab and the jobs will be executed as root.
It should be ok to take snapshots as root but take care when you restore things (BIT restore process backup the files that it will change).
If you only want to backup/restore some user folders than I don't recommend you to run it as root.

OK Dan thanks. Can I just clarify two points please ?

1. You wrote ... "(BIT restore process backup the files that it will change)."
I don't quite understand what you are saying here I'm afraid.

2. Aside from that, it looks like I now have a way of using BiT on OpenSuse 11.0, but you do say "If you only want to backup/restore some user folders than I don't recommend you to run it as root." That's fair comment and I would rather run it as an ordinary user if possible, as I can under Ubuntu 9.04.

With that in mind, and everything that has gone before, the plain-user issue seems to be permissions, as demonstrated by the differences shown in my response on 2009-12-03 which shows the differences between the ls command on each system.

Is there not some way of configuring things so that these appear the same ? Is there something that can be done in terms of configuring /etc/mtab (or is it /etc/fstab ?).

Thanks,

Reler

Hi,

1. Let's say that you have the file "a.txt" that contains "ABC". When you take a snapshot, BIT will backup this file.
If you want to restore it from the snapshot there is nothing to do because you didn't change the file yet.
Then you change it to "BCD". Now if you want to restore the file, BIT will need to change your "a.txt" file , so it will create a backup file called "abc.txt.backup.<date>" and then it will restore the file. This way you still have the original file in case you pressed restore by error.

2. Only if you use a linux filesystem that support users/groups/rights. But don't worry, if you restore a file BIT will try to restore user/group/rights from a special file.

Regards,
Dan