← Back to team overview

nssbackup-team team mailing list archive

[Bug 617473] Re: amd64 ftp gio mount error

 

Yes this works an my thinkpad and eee on i386 base packages.

Got the 0.3.1 packages this morning.

+++-==============-==============-============================================
un  gvfs-fuse      <keine>        (keine Beschreibung vorhanden)

Do i need this package?

When mounted by hand in nautilus the .gvfs folder is empty, but in
nautilus the mount is full accessible. This method seems not to be used.

eric@agamemnon:~/.gvfs$ ls -l
insgesamt 0

The 0.3.1 does the same, response the mount error but in nautilus the
full accessible mount appears in the same moment. The mount goes well
but nssbackup did not see that.

2010-08-14 12:38:09,398 - INFO in SBConfigGTK.__show_connect_remote_dialog(1589): Connect to remote destination
2010-08-14 12:38:09,398 - DEBUG in SBConfigGTK.__show_connect_remote_dialog(1600): User input in dialog 'connect to host'
2010-08-14 12:38:09,399 - DEBUG in SBConfigGTK.__show_connect_remote_dialog(1601):   Service: 102
2010-08-14 12:38:09,399 - DEBUG in SBConfigGTK.__show_connect_remote_dialog(1602):   Server: 192.168.1.250
2010-08-14 12:38:09,399 - DEBUG in SBConfigGTK.__show_connect_remote_dialog(1603):   Port: 
2010-08-14 12:38:09,400 - DEBUG in SBConfigGTK.__show_connect_remote_dialog(1604):   Path: /agamemnon
2010-08-14 12:38:09,400 - DEBUG in SBConfigGTK.__show_connect_remote_dialog(1605):   User: backup
2010-08-14 12:38:09,400 - DEBUG in SBConfigGTK.__show_connect_remote_dialog(1606):   Pass: ******

2010-08-14 12:38:09,403 - DEBUG in pathparse.construct_remote_uri_from_tupel(299): construct_from_remote_tupel: ftp://backup:anfang@192.168.1.250/agamemnon
2010-08-14 12:38:09,404 - DEBUG in pathparse.set_and_parse_uri(210): UriParser:
Display name: ftp://backup@192.168.1.250/agamemnon
URI scheme: ftp
eff. scheme: ftp
Hostname: `192.168.1.250`
Path: `/agamemnon`
Port: None
Username: `backup`
Password: `******`
2010-08-14 12:38:09,404 - DEBUG in _gio_fam.set_initialize_callback(62): set_initialize_callback: <bound method SBconfigGTK._mount_done_cb of <nssbackup.ui.SBConfigGTK.SBconfigGTK object at 0x1751310>>
2010-08-14 12:38:09,405 - DEBUG in pathparse.set_and_parse_uri(210): UriParser:
Display name: ftp://backup@192.168.1.250/agamemnon
URI scheme: ftp
eff. scheme: ftp
Hostname: `192.168.1.250`
Path: `/agamemnon`
Port: None
Username: `backup`
Password: `******`
2010-08-14 12:38:09,428 - INFO in _gio_fam.initialize(96): Initializing GIO File Access Manager.
2010-08-14 12:38:09,429 - DEBUG in pathparse.query_mount_uri(247): get_mount_uri: ftp://backup@192.168.1.250/agamemnon
2010-08-14 12:38:09,429 - DEBUG in _gio_utils.mount(261): Mount path: ftp://backup@192.168.1.250/agamemnon
2010-08-14 12:38:09,429 - DEBUG in _gio_utils._is_local(211): Given path is not local
2010-08-14 12:38:09,627 - DEBUG in pathparse.query_mount_uri(247): get_mount_uri: ftp://backup@192.168.1.250/agamemnon
2010-08-14 12:38:09,628 - DEBUG in _gio_utils._set_mount_flag(235): Path_mount_info: Path: `ftp://backup@192.168.1.250/agamemnon`
Eff. path: `None`
Mounted: True
2010-08-14 12:38:09,628 - DEBUG in _gio_utils._mount_done_cb(369): Calling additional callback
2010-08-14 12:38:09,628 - DEBUG in pathparse.query_mount_uri(247): get_mount_uri: ftp://backup@192.168.1.250/agamemnon
2010-08-14 12:38:09,628 - DEBUG in _gio_utils.get_eff_path(251): URI: ftp://backup@192.168.1.250/agamemnon
2010-08-14 12:38:09,628 - DEBUG in _gio_utils.get_eff_path(254): Effective path: `None`
2010-08-14 12:38:09,628 - ERROR in _gio_fam._mount_cb(165): Error in mount callback function: Unable to mount target
2010-08-14 12:38:09,628 - DEBUG in _gio_fam._mount_cb(172): Calling additional callback in gio_fam._mount_cb: <bound method SBconfigGTK._mount_done_cb of <nssbackup.ui.SBConfigGTK.SBconfigGTK object at 0x1751310>>
2010-08-14 12:38:09,628 - DEBUG in SBConfigGTK._mount_done_cb(1633): GUI._mount_done_cb: error: Unable to mount target

-- 
amd64 ftp gio mount error
https://bugs.launchpad.net/bugs/617473
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to nssbackup.



References