Export png fails with: Invalid cross-device link

Bug #1993294 reported by Heinrich Schuchardt
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
inkscape (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Export png fails with "Invalid cross-device link" if /tmp is mount as tmpfs.

I have stored https://assets.ubuntu.com/v1/ce518a18-CoF-2022_solid+O.svg as file /home/user/CoF-2022_solid+O.svg.
I open inkscape on the command line with inkscape CoF-2022_solid+O.svg.
I select export png and try to export to my home directory.
A file of length 0 is created.
The console shows an error message:
"boost::filesystem::copy_file: Invalid cross-device link: "/tmp/ink_ext_CF77T1", "/home/user/temp/cof.png"

The following mounts exist:

/dev/mapper/vgkubuntu-home on /home type ext4 (rw,relatime)
zfsdt@workstation5:~/temp$ mount | grep '\/tmp'
tmpfs on /tmp type tmpfs (rw,relatime,inode64)

So /tmp and /home are actually separate devices.

ln -s /home/user/temp/cof.png /tmp/cof.png
works fine.

ln /home/user/temp/cof.png /tmp/cof.png
fails with
ln: failed to create hard link '/tmp/cof.png' => '/home/user/temp/cof.png': Invalid cross-device link

Exporting to /tmp works.

Inkscape should not create hardlinks on /tmp as /tmp typically is a tmpfs.

Revision history for this message
Heinrich Schuchardt (xypron) wrote :

Inkscape 1.3-dev (1:1.2.0-alpha1+devel+202210180739+994e1ec499) from ppa:inkscape.dev/trunk works fine. We should update the package.

Revision history for this message
Heinrich Schuchardt (xypron) wrote :

Debian has 1.2.1+ds-1 in sid.

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

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

Changed in inkscape (Ubuntu):
status: New → Confirmed
Revision history for this message
Torbjörn Rathsman (milasudril) wrote :

Could this be related to a recent break of syscall copy_file_range.

Revision history for this message
Torbjörn Rathsman (milasudril) wrote :

Problem appears to be fixed in Inkscape 1.2.2 (1:1.2.2+202212051552+b0a8486541). Please update the official package ASAP.

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.