maemo.org Bugzilla – Bug 3675
backup will loop nearly infinitely for directories containing pairs of symlinks that do not point to descendants because backup is following them
Last modified: 2010-01-15 00:30:57 UTC
You need to
before you can comment on or make changes to this bug.
i discovered this while writing the testcase for bug 3591
Created an attachment (id=922) [details]
Created an attachment (id=923) [details]
i made this testcase and RST38h tested it (thanks). i'm attaching it for
don't leave your device plugged into a charger :)
1. click attachment 923 [details] and let it install
2. install strace and run strace -f -p `pidof maemo-launcher`
3. run backup and ask it to backup settings
backup completes (relatively quickly)
backup will probably never complete (technically it might eventually since
we're only pairwise nesting until we hit max path depth, but it's a really
expensive nest), as long as you aren't charging, I'm willing to give you a
cookie if your device finishes (any message) its backup w/o running out of
Have you tested this against Fremantle?
I'm not sure I have the skills to follow the steps of comment #3
(In reply to comment #3)
> 1. click attachment 923 [details] [details] and let it install
Fremantle currently only offers to download, not directly install.
Opening the local package in File Manager and choosing Application manager as
the app to open with currently does not seem to work in Fremantle.
Hence currently unable to test in Fremantle.
You need root and xterm to install packages directly.
(In reply to comment #6)
> You need root and xterm to install packages directly.
I tried this too - "sudo gainroot" and "apt-get install", but how does the URI
have to look like? :-/
you'll have to use "dpkg -i bugs-maemo-3675-0.1.deb" instead of apt*
(In reply to comment #3)
> 3. run backup and ask it to backup settings
Sigh, in the current Fremantle version I always get "Application Backup not
responding" after choosing the Data I want to backup.
This has been fixed in package
which is part of the internal build version
(Note that 2009 is the year and the number after is the week.)
Any public update released with or after this build version will include the
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
given that libssoautologin is some specific victim, that means that the backup
team didn't fix this. please import again.
Do not edit aliases. Thanks.
Internal comment: "This was fixed 3 months ago and is available in
libssoautologin 1.0.7. Please close it."
timeless, if you think that this does not cover the entire issue, feel free to
open an internal issue...
andre: i filed this bug against backup. there is no reason for a bug with a
testcase that you could reproduce should be marked as fixed.
especially when the second bug is currently assigned to someone and is *NOT*