Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

Bug #1612708 reported by prof2004
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 16.04.1 LTS

colord:
  Installiert: 1.2.12-1ubuntu1
  Installationskandidat: 1.2.12-1ubuntu1
  Versionstabelle:
 *** 1.2.12-1ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

Under Ubuntu 14.04 LTS I have created NAS access by using 'gvfs-mount smb://nasdo/public'. It is linked to '/run/user/1000/gvfs/ als smb-share:server=nasdo,share=public' and I have created a Symbolic Link to this point with 'ln -s /run/user/1000/gvfs/smb-share\:server\=nasdo\,share\=public ~/nasdo_public'. Using this link folders, and files on the NAS have been accessable with r/w from Ubuntu 14.04 LTS. This is, what I expect from 16.04, too.

Since I have upgraded to ubuntu 16.04 LTS a few days ago, all the links seem to be the same, but opening a file does not work. It comes to an input/output error. I can use the links to folders to navigate, but there is no chance to open e.g. an LibreOffice Calc Sheet, nor do I have access to mail folder via Thunderbird.

Using gvfs-mount creates a shared folder in Nautilus called public. Using this way to access the NAS, and open the Calc file works with ubuntu 16.04 LTS fine.

Locking to the syslog while trying to open a file creates the following entries:
Aug 12 16:47:19 UDO systemd[1]: Started Hostname Service.
Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (process:8645): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Der angegebene Ort ist nicht eingehängt
Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (process:8663): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Der angegebene Ort ist nicht eingehängt
Aug 12 16:47:48 UDO systemd[1]: Started CUPS Scheduler.
Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
Aug 12 16:50:15 UDO systemd[1]: Started CUPS Scheduler.
Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
Aug 12 16:54:32 UDO systemd[1]: Started CUPS Scheduler.
Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
Aug 12 16:55:01 UDO dbus[2427]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Aug 12 16:55:01 UDO systemd[1]: Starting Hostname Service...
Aug 12 16:55:01 UDO dbus[2427]: [system] Successfully activated service 'org.freedesktop.hostname1'
Aug 12 16:55:01 UDO systemd[1]: Started Hostname Service.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in colord (Ubuntu):
status: New → Confirmed
Revision history for this message
Marc Neiger (marc-i) wrote :

oddly enough it depends on how one accesses the remote files.
opening and modifying a text file with xed work on direct access (through /run/user ....)
through the symbolic link, I can read it but attempt to save after modifications will fail

Could not save the file xxxx
xed cannot handle file: locations in write mode. Please check that you typed the location correctly and try again.

other text editors will fail differently, leafpad truncates the file to 0 bytes!

Revision history for this message
mohican (mohican) wrote :

I ran into a bug that may be the same as yours :

My data is on a different partition than the system.
I use symbolic links in the ~ directory to access these files.

e.g. /home/me/Download is a symbolic link to /media/DATA/me/Download/

When I try to delete a file from the Download folder, accessing it through the symbolic link, I have a message that says (I translate) 'unable to move the file to the trash do you want to delete it completely ?' or (using Thunar on Xubuntu 16.04) **"invalid cross-device link"**

This is the same whether the data partition is EXT4 or NTFS formated.

When I access the file directly from the /media/DATA partition I can move it into the trash normally.

Revision history for this message
mohican (mohican) wrote :

But differently from you I can read and write files accessed through the symbolic link.

It's only moving them to the trash that fails.

- Using the 'move to trash' menu fails.
- Manually cutting the file then trying to paste it into the trash fails.
- Manually cutting the file then trying to paste it into the /media/DATA/.Trash-1000/files/ directory works.

Revision history for this message
mohican (mohican) wrote :

My bug appears to be bug #1449112
There's a patch for it. If you try the patch (only for Ubuntu 16.04) you may find out whether your bug is the same as mine.

Revision history for this message
prof2004 (jdokupil) wrote :

I am running ubuntu 16.04.1, sobthe patch cannot be applied.

Revision history for this message
prof2004 (jdokupil) wrote :

Reading the bugs around colord, it seams to me, that this error is not related to colord.
It is most propably a problem of gvfs.

I will try to link this bug to gvfs. If there is any operator available, pls support to re-link this bug to gvfs.

It is a critical error, because using the symbolic links is important for using the system.
You can find work arounds, but I am thinking about downgrading to ubuntu 14.04 LTS.

Peter Meiser (meiser79)
affects: colord (Ubuntu) → gvfs (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.