After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 326705 - nautilus should use mdns hostname for bookmark/keyring
nautilus should use mdns hostname for bookmark/keyring
Status: RESOLVED DUPLICATE of bug 555436
Product: nautilus
Classification: Core
Component: Navigation
2.13.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-12 10:02 UTC by Frej Soya
Modified: 2008-11-07 10:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Frej Soya 2006-01-12 10:02:14 UTC
Please describe the problem:
Nautilus saves the ip/port (Auth realm also for keyring) as bookmark/keyring
name, but that is not static in a mdns/zeroconf enviroment. So after
reboot/relogin the keyring is dead.

could use mdns hostname (host.local) and "service name" instead? 

Steps to reproduce:



Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Frej Soya 2006-01-12 10:06:56 UTC
'dead' might be a strong word.

The saved info is not valid for keyring/bookmarks when the host restarts gnome-user-share (relogin) or the ip could change (reboot). Sorry for the spam :)
Comment 2 David Zeuthen (not reading bugmail) 2008-11-04 03:42:21 UTC
(In reply to comment #0)
> Please describe the problem:
> Nautilus saves the ip/port (Auth realm also for keyring) as bookmark/keyring
> name, but that is not static in a mdns/zeroconf enviroment. So after
> reboot/relogin the keyring is dead.
> 
> could use mdns hostname (host.local) and "service name" instead? 

Looks like bug 555436 should solve this. Suggest to close as dupe (or at least reassign to gvfs).
Comment 3 Cosimo Cecchi 2008-11-07 10:26:13 UTC

*** This bug has been marked as a duplicate of 555436 ***