Ubuntu
sshfs-fuse package

Ubuntu lunar. Error after upgrade to 3.7.3-1.1

Bug #2007750 reported by testpi
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
sshfs-fuse (Ubuntu)
Fix Released
Medium
Erich Eickmeyer
Ubuntu ubuntu-23.04-beta

Bug Description

Use ubuntu lunar 23.04. After upgrade to 3.7.3-1.1, when I run the application I get an error: "sshfs: symbol lookup error: sshfs: undefined symbol: fuse_new_31, version FUSE_3.1"
After downgrade to 3.7.2-1, all works fine.

See original description
testpi (testpi5)
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in sshfs-fuse (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul Tobias (tobias.pal) wrote :

Downgrading to `sshfs_3.7.3-1_amd64` from https://launchpad.net/ubuntu/lunar/amd64/sshfs/3.7.3-1 works too.
So it seems to be a problem introduced by 3.7.3-1.1

With sshfs_3.7.3-1.1 I get a symbol lookup error:
$ sshfs
sshfs: symbol lookup error: sshfs: undefined symbol: fuse_new_31, version FUSE_3.1

But sshfs_3.7.3-1 works fine:
$ sshfs
missing host
see `sshfs -h' for usage

Revision history for this message
Jonathan Kamens (jik) wrote :

If I may wax philosophical for a moment, I think there is kind of an understanding between Canonical and those of us who run prereleases to help find issues before they are released to the world: in exchange for our free labor and for us allowing ourselves to be occasionally inconvenienced with something we rely on breaks in a prerelease, Canonical endeavors to deal with breakage like this relatively quickly. I'm disappointed that's not happening with this issue.

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote (last edit ):

Sadly, this isn't a Canonical thing (Canonical only manages the main repository, this package is in the universe repository which is community supported). Furthermore, this was auto-sync'd from Debian, which means it's an upstream issue, but I couldn't find a matching upstream bug.

I might be taking on this bug if reverting the changes in the -1.1 done upstream in Debian do the trick. Otherwise, reverting to 3.7.2 is a bigger task.

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Looks like all this is going to take is a no-change rebuild in order to work again, but the new fuse3 is taking some time to work through the autopkgtest queue, so have some patience.

Changed in sshfs-fuse (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Erich Eickmeyer (eeickmeyer)
importance: Undecided → Medium
milestone: none → ubuntu-23.04-beta
Erich Eickmeyer (eeickmeyer)
Changed in sshfs-fuse (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sshfs-fuse - 3.7.3-1.1build1

---------------
sshfs-fuse (3.7.3-1.1build1) lunar; urgency=medium

  * No-change rebuild against fuse3 3.14.0 (LP: #2007750)

 -- Erich Eickmeyer <email address hidden> Tue, 28 Feb 2023 10:49:50 -0800

Changed in sshfs-fuse (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
isak paslı (crypt5306) wrote :

Where can I download the mentioned version?
(sshfs-fuse - 3.7.3-1.1build1)

Revision history for this message
Oibaf (oibaf) wrote :

It's in Ubuntu lunar, just make sure to update your packages.

Revision history for this message
isak paslı (crypt5306) wrote (last edit ):

Unfortunately i cant update online:( I use this package on proxmox. i must install from offline deb package

Revision history for this message
Oibaf (oibaf) wrote :

Download and install it from here:
https://launchpad.net/ubuntu/+source/sshfs-fuse

Revision history for this message
isak paslı (crypt5306) wrote :

thank you so much Oibaf

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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