Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

got stuck if backup destination is an encryted mobile harddrive #81

Open
GoogleCodeExporter opened this issue Sep 24, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

1. I have an USB external HD. I encrypted the entire disk using luks. After
the plug-in, Ubuntu will ask me the passphrase and mount it automatically.
But, if such an HD is connected, I couldn't create new backup in flyback
v0.6. I tried to start flyback from my shell. Whenever I click
"Double-click here to create a new backup," I can see "can not open
/media/M500G" on my shell.

2. If I disconnect the HD, I can go to the interface to select backup
destination and source. But of course, without external HD, I couldn't
select the backup destination.

What is the expected output? What do you see instead?
I wish to be able to select the destination by its path, such as
/media/backupHD. I can do this in versions before 0.5. But it seems that
since v0.5, flyback has changed and seeks to find backup destination
automatically. Is this the reason of the problem?

What version of the product are you using? On what operating system?
I am using flyback v6.1_r111 on Ubuntu Linux 9.10. 

I can provide more information if needed. 

Original issue reported on code.google.com by [email protected] on 27 Jan 2010 at 5:34

@GoogleCodeExporter
Copy link
Author

can you give me the entire shell output?

Original comment by [email protected] on 19 Feb 2010 at 3:49

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 19 Feb 2010 at 4:52

  • Changed state: NeedInfo
  • Added labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Now I notice the problem has been fixed in v.0.6.5-1

Original comment by [email protected] on 21 Nov 2010 at 9:44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant