[Expired for glib2.0 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: glib2.0 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launch
> using what protocol? did you mount those using nautilus?
mounted with Nautilus, using SSH protocol
My longterm workaround has been to use (VanDyke) SecureFX, either under
Linux/Wine or Windows (on another/third host).
Recently started using SecureCRT (Linux) in beta, which does not yet
have
> This affects ANY attempt to transfer files (using Nautilus 2.30.1)
between two hosts with Ubuntu 10.04 LTS on both, or from 10.04 LTS to
10.10
using what protocol? did you mount those using nautilus?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
per #3
> is that a local issue?
This appears to be general for 10.04 LTS
> is the issue solved in recent versions?
NO, not yet resolved by latest updates to 10.04 LTS
(YES, solved in Ubuntu 10.10 or later, which now use Nautilus 2.23.0 )
--
You received this bug notification because you are a
per #2
> * Is this reproducible?
YES
> * If so, what specific steps should we take to recreate this bug
This affects ANY attempt to transfer files (using Nautilus 2.30.1) between two
hosts with Ubuntu 10.04 LTS on both, or from 10.04 LTS to 10.10
I have noted this on a number of occasions, on
is that a local issue? is the issue solved in recent versions?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in ubuntu.
https://bugs.launchpad.net/bugs/738462
Title:
Nautilus not preserving timestamps (Lucid)
--
desktop-
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: glib2.0 (Ubuntu)
IMHO, Bug #215499 was not properly resolved.
IMHO, Bug #319063 should have addressed this, OR been changed to next
LTS release (from Intrepid).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in ubuntu.
https://bugs.launchpad.
