Just in case it's useful, I reproduced the regression with a hardy chroot, using only command line tools:
1. Install samba on outside system
2. Kill all gvfs stuff (outside and inside chroot):
$ ps ux|grep gvfs|awk '{print $2}'|xargs kill
3. Mount gvfs smb and list it in hardy chroot:
$ dchroot -c hardy [hardy] $ dbus-launch bash [hardy] gvfs-mount smb: [hardy] $ gvfs-ls smb:// WORKGROUP
4. Now install gvfs and gvfs-backends from http://ppa.launchpad.net/vorlon/ppa/ubuntu in hardy chroot
5. Re-do step 2 and 3; gvfs-ls will print nothing
Just in case it's useful, I reproduced the regression with a hardy chroot, using only command line tools:
1. Install samba on outside system
2. Kill all gvfs stuff (outside and inside chroot):
$ ps ux|grep gvfs|awk '{print $2}'|xargs kill
3. Mount gvfs smb and list it in hardy chroot:
$ dchroot -c hardy
[hardy] $ dbus-launch bash
[hardy] gvfs-mount smb:
[hardy] $ gvfs-ls smb://
WORKGROUP
4. Now install gvfs and gvfs-backends from http:// ppa.launchpad. net/vorlon/ ppa/ubuntu in hardy chroot
5. Re-do step 2 and 3; gvfs-ls will print nothing